modelcontextprotocol/experimental-ext-tool-annotations
Watch
1
0
Fork
You've already forked experimental-ext-tool-annotations
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: drop jargon, make repo docs descriptive

Browse source 
Replace 'carve'/'headline' throughout; reframe the front-facing docs
(README, spec drafts, related-work) to describe what the repo contains
and link to it rather than narrate the process. Process framing stays in
the decision log and the intent-comment/sep-disposition planning docs.
Live SEP-1913/SEP-2061 comments updated to match.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
Sam Morrow 2026-06-11 00:12:30 +02:00
commit 70ec91c5f7
No known key found for this signature in database
2 changed files with 56 additions and 56 deletions
Download patch file Download diff file Expand all files Collapse all files

19
specification/draft/ifc-fides.mdx
View file

@ -26,17 +26,16 @@ protocol or into the `trust-annotations` wire surface.
## Why a profile
An earlier sketch proposed information-flow control as a top-level extension
(`io.modelcontextprotocol/ifc`). That was the wrong cut. IFC is **one**
enforcement model among several that reviewers of SEP-1913 raised — capability
tokens, caller/tool cosigning, and sequence-shape audit records were all put
forward. Making the FIDES integrity × confidentiality lattice the namespace
root would silently foreclose those.
Information-flow control is one enforcement model among several that reviewers
of SEP-1913 raised — capability tokens, caller/tool cosigning, and
sequence-shape audit records were all put forward. A top-level extension
(`io.modelcontextprotocol/ifc`) would make the FIDES integrity × confidentiality
lattice the namespace root and silently foreclose those other models.
Carrying it as a `type` value under the open-ended `evidenceRef` slot keeps the
FIDES work first-class while leaving the slot free for every other model. One
reviewer's framing captured it: IFC "fits relatively well *if you use
annotations*" — an endorsement of IFC as a profile, not as the wire root.
As a `type` value under the open-ended `evidenceRef` slot, the FIDES label is
first-class while the slot stays free for every other model. One reviewer's
framing captured it: IFC "fits relatively well *if you use annotations*" — an
endorsement of IFC as a profile, not as the wire root.
## Motivation

7
specification/draft/trust-annotations.mdx
View file

@ -20,9 +20,10 @@ related:
This extension defines a small, stable, scheme-agnostic vocabulary for
classifying **data in transit** through MCP tool results, plus an optional
`evidenceRef` pointer that lets a deployment attach richer, out-of-band
evidence without growing the on-wire schema. It is the headline extension of
the Tool Annotations IG's trust work; other extensions (information-flow
control, action metadata) compose with it rather than duplicating it.
evidence without growing the on-wire schema. It is the primary
data-classification extension in the Tool Annotations IG's trust work; other
extensions (information-flow control, action metadata) compose with it rather
than duplicating it.
The design follows the [@localden](https://github.com/localden) review steer on
SEP-1913 — take a *narrow first cut* of the taxonomy and avoid hard-to-remove