modelcontextprotocol / modelcontextprotocol/ext-apps
No way to mark a secondary tool as visible only to app
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 387
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 6
Description
Describe the bug
Currently, visibility is at the _meta UI level. However, tools that the UI might call must be visible to the model. There's no way to have app-only tools that don't pollute the model's context.
Maybe this is an inherent problem but it would be nice to able to mark a tool as app-only so that our apps can create the tools they need without exposing them to normal agent usage.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how tool visibility is represented at the meta UI level and how tools are exposed to the model. Determine whether the protocol can distinguish app-only tools from normal agent tools; done means an agreed mechanism that lets apps use secondary tools without adding them to the model’s context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100