No way to mark a secondary tool as visible only to app

Open
#732 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
typescript
Domain
api, backend-api-design

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.

Description

bug

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.

Dominant language
TypeScript
Stars
2.9k
Forks
387
Avg merge
3h 21m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/ext-apps

All issues in modelcontextprotocol/ext-apps

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.