address PR review comments

- Change default visibility to ["model", "apps"]
- Add deprecation notice for flat ui/resourceUri format
- Add McpUiToolMeta and McpUiToolVisibility to spec.types.ts
- Improve tools/list and tools/call behavior wording

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: antonpk1

specification/draft/apps.mdx

@@ -251,9 +251,9 @@ interface McpUiToolMeta {
   /** URI of UI resource for rendering tool results */
   resourceUri?: string;
   /**
-   * Who can access this tool. Default: ["model"]
+   * Who can access this tool. Default: ["model", "apps"]
    * - "model": Tool visible to and callable by the agent
-   * - "apps": Tool callable by ui apps from this server
+   * - "apps": Tool callable by apps from this server only
    */
   visibility?: Array<"model" | "apps">;
 }
@@ -264,10 +264,14 @@ interface Tool {
   inputSchema: object;
   _meta?: {
     ui?: McpUiToolMeta;
+    /** @deprecated Use `ui.resourceUri` instead. Will be removed before GA. */
+    "ui/resourceUri"?: string;
   };
 }
 ```
 
+> **Deprecation notice:** The flat `_meta["ui/resourceUri"]` format is deprecated. Use `_meta.ui.resourceUri` instead. The deprecated format will be removed before GA.
+
 Example (tool visible to both model and apps):
 
 ```json
@@ -316,11 +320,11 @@ Example (app-only tool, hidden from model):
 
 #### Visibility:
 
-- `visibility` defaults to `["model"]` if omitted (standard MCP behavior)
+- `visibility` defaults to `["model", "apps"]` if omitted
 - `"model"`: Tool is visible to and callable by the agent
 - `"apps"`: Tool is callable by apps from the same server connection only
-- Host MUST NOT include tools with `visibility: ["apps"]` in the agent's tool list
-- Host MUST reject `tools/call` requests from apps for tools that don't include `"apps"` in visibility
+- **tools/list behavior:** Host MUST NOT include tools in the agent's tool list when their visibility does not include `"model"` (e.g., `visibility: ["apps"]`)
+- **tools/call behavior:** Host MUST reject `tools/call` requests from apps for tools that don't include `"apps"` in visibility
 - Cross-server tool calls are always blocked for app-only tools
 
 #### Benefits:
@@ -1096,7 +1100,7 @@ This proposal synthesizes feedback from the UI CWG and MCP-UI community, host im
 
 - Nested `_meta.ui` structure groups all UI-related metadata cleanly
 - Array format (`["model", "apps"]`) allows flexible combinations
-- Default `["model"]` preserves standard MCP behavior for existing tools
+- Default `["model", "apps"]` allows both agent and apps to access tools
 - `"apps"` scope is per-server, preventing cross-server tool calls
 - Cleaner than OpenAI's two-field approach (`widgetAccessible` + `visibility`)
 

src/spec.types.ts

@@ -371,3 +371,22 @@ export interface McpUiResourceMeta {
   /** @description Visual boundary preference - true if UI prefers a visible border. */
   prefersBorder?: boolean;
 }
+
+/**
+ * @description Tool visibility scope - who can access the tool.
+ */
+export type McpUiToolVisibility = "model" | "apps";
+
+/**
+ * @description UI-related metadata for tools.
+ */
+export interface McpUiToolMeta {
+  /** @description URI of UI resource for rendering tool results. */
+  resourceUri?: string;
+  /**
+   * @description Who can access this tool. Default: ["model", "apps"]
+   * - "model": Tool visible to and callable by the agent
+   * - "apps": Tool callable by apps from this server only
+   */
+  visibility?: McpUiToolVisibility[];
+}