Skip to content

fix: prefer tool title in app view chrome - #749

Open
Chipagosfinest wants to merge 1 commit into
modelcontextprotocol:mainfrom
Chipagosfinest:agent/use-tool-title-for-app-view
Open

fix: prefer tool title in app view chrome#749
Chipagosfinest wants to merge 1 commit into
modelcontextprotocol:mainfrom
Chipagosfinest:agent/use-tool-title-for-app-view

Conversation

@Chipagosfinest

Copy link
Copy Markdown

What changed

  • updates the basic host to label tool-instantiated app chrome with Tool.title, falling back to Tool.name
  • adds the same behavior as a draft specification recommendation

Why

App views currently expose programmatic identifiers such as get_report_app even when a tool already provides a human-readable title. Reusing the standard Tool.title field fixes the user-facing mismatch without adding redundant app-specific metadata or coupling the display label to the callable tool name.

This also matches the broader Mini App pattern where host-provided chrome uses human-readable app/action metadata while machine identifiers remain internal.

Closes #740.

Validation

  • npm run --workspace examples/basic-host build
  • npm run prettier
  • repository pre-commit hook: npm run build:all

@Chipagosfinest
Chipagosfinest marked this pull request as ready for review August 17, 2026 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

App view frame is labeled with the tool name, not its title — no _meta.ui field to name a view

1 participant