Skip to content

Commit 4137e6a

Browse files
dsp-antdsp-ant
authored
Merge pull request modelcontextprotocol#2615 from SamMorrowDrums/sammorrowdrums/tool-annotations-ig-charter
docs: add Tool Annotations Interest Group charter
2 parents b9c00aa + b4a909c commit 4137e6a

2 files changed

Lines changed: 96 additions & 0 deletions

File tree

‎docs/community/tool-annotations/charter.mdx‎

Lines changed: 90 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,90 @@
1+
---
2+
title: Tool Annotations Charter
3+
description: Charter for the MCP Tool Annotations Interest Group.
4+
---
5+
6+
## Group Type
7+
8+
**Interest Group**
9+
10+
## Mission Statement
11+
12+
The Tool Annotations Interest Group explores the role of tool annotations in enabling safe, usable agentic systems across the MCP ecosystem. Today, six independent SEPs propose annotation changes, each solving real problems but lacking the coherent, cross-cutting perspective that a dedicated group can bring. The IG gathers use cases from server and client authors, evaluates existing and proposed annotations, and considers the long-term future of the annotation model, including whether runtime annotations, tool response annotations, and other extensions belong in the protocol.
13+
14+
## Scope
15+
16+
### In Scope
17+
18+
- **Evaluation of existing annotations**: Assess whether the current set of tool annotations (`readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`) adequately serves server and client authors
19+
- **Discussion of proposed annotations**: Review and provide feedback on SEPs proposing new or modified tool annotations (trust/sensitivity, agency, model preferences, and others)
20+
- **Future of the annotation model**: Explore whether runtime annotations, tool response annotations, or structural changes to the annotation system are worth adding to the protocol
21+
- **Use-case gathering**: Collect real-world use cases from server authors, client authors, and host applications to ground annotation decisions in practical needs
22+
- **Problem statements and recommendations**: Produce recommendations for Working Groups or SEP authors on annotation design, coherence, and prioritization
23+
24+
### Out of Scope
25+
26+
- **Binding specification changes**: The IG produces recommendations, not binding decisions; specification changes are made through the SEP process
27+
- **Implementation work**: Building SDK features or reference implementations (may be explored in the [experimental repo](https://github.com/modelcontextprotocol/experimental-ext-tool-annotations) but is not the IG's primary purpose)
28+
- **Non-annotation tool changes**: Changes to tool discovery, invocation, or lifecycle that do not relate to annotations
29+
- **Resource annotations**: While related, resource-level annotation work is tracked separately unless it directly intersects with tool annotation design
30+
31+
### Related Groups
32+
33+
- **Security IG** - Trust and sensitivity annotations ([SEP-1913](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1913)) span both groups' interests
34+
- **[Skills Over MCP WG](/community/skills-over-mcp/charter)** - Skill-level metadata may interact with tool annotations for discovery and filtering
35+
36+
## Leadership
37+
38+
| Role | Name | Organization | GitHub | Term |
39+
| ----------- | -------------- | ------------ | ---------------------------------------------------- | ------- |
40+
| Facilitator | Sam Morrow | GitHub | [@SamMorrowDrums](https://github.com/SamMorrowDrums) | Initial |
41+
| Facilitator | Robert Reichel | OpenAI | [@rreichel3](https://github.com/rreichel3) | Initial |
42+
43+
## Membership
44+
45+
| Name | Organization | GitHub | Discord | Level |
46+
| -------------- | ------------ | ---------------------------------------------------- | ------- | ----------- |
47+
| Sam Morrow | GitHub | [@SamMorrowDrums](https://github.com/SamMorrowDrums) | | Facilitator |
48+
| Robert Reichel | OpenAI | [@rreichel3](https://github.com/rreichel3) | | Facilitator |
49+
| Matt Carey | Cloudflare | [@mattzcarey](https://github.com/mattzcarey) | | Participant |
50+
| Kapil Sharma | Microsoft | [@kapil8811](https://github.com/kapil8811) | | Participant |
51+
52+
## Operations
53+
54+
| Meeting | Frequency | Duration | Purpose |
55+
| ---------- | --------- | -------- | --------------------------------------------- |
56+
| Discussion | TBD | TBD | Use-case sharing, annotation review, open Q&A |
57+
58+
Discord: [#tool-annotations-ig](https://discord.com/channels/1358869848138059966/1482836798517543073)
59+
60+
## Discussion Topics
61+
62+
The following SEPs and themes form the IG's initial discussion agenda. This list is not exhaustive and will evolve as the group identifies new areas of interest.
63+
64+
### Active SEPs Under Discussion
65+
66+
| SEP | Title | Status | Author |
67+
| ---------------------------------------------------------------------------------- | ---------------------------------- | ------ | ------------------------------------------------------------------------------------------------ |
68+
| [SEP-1862](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1862) | Tool Resolution (preflight checks) | Draft | [@SamMorrowDrums](https://github.com/SamMorrowDrums) |
69+
| [SEP-1913](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1913) | Trust and Sensitivity Annotations | Draft | [@SamMorrowDrums](https://github.com/SamMorrowDrums), [@rreichel3](https://github.com/rreichel3) |
70+
| [SEP-1984](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1984) | Comprehensive Tool Annotations | Draft | [@sambhav](https://github.com/sambhav) |
71+
| [SEP-2417](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2417) | Model Preferences for Tools | Draft | [@ProductOfAmerica](https://github.com/ProductOfAmerica) |
72+
73+
### Open Questions
74+
75+
- Should runtime annotations (annotations that change between invocations) be added to the protocol?
76+
- Are additional static annotations worth standardizing, and which serve both server and client authors?
77+
- Should tool _response_ annotations be added to the protocol?
78+
- How should annotations interact with trust, security, and human-in-the-loop requirements?
79+
- What is the right level of granularity - a few well-defined hints vs. a richer, extensible vocabulary?
80+
81+
## Resources
82+
83+
- [Tool Annotations as Risk Vocabulary](https://blog.modelcontextprotocol.io/posts/2026-03-16-tool-annotations/) - blog post framing the motivation for this work
84+
- [Experimental repo](https://github.com/modelcontextprotocol/experimental-ext-tool-annotations) - repository for the Tool Annotations Interest Group
85+
86+
## Changelog
87+
88+
| Date | Change |
89+
| ---------- | --------------- |
90+
| 2026-04-20 | Initial charter |

‎docs/docs.json‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -500,6 +500,12 @@
500500
"community/triggers-events/charter"
501501
]
502502
},
503+
{
504+
"group": "Interest Group Charters",
505+
"pages": [
506+
"community/tool-annotations/charter"
507+
]
508+
},
503509
{
504510
"group": "Roadmap",
505511
"pages": [

0 commit comments

Comments
 (0)