Tool Manifest
The declared set of tools, resources and prompts an MCP server exposes to a client — the machine-readable statement of what an agent is able to reach.
- StatusIndustry term
- AdoptionWidely used
- LayerIntelligence
Why it matters
This is the first widely adopted artifact where an agent's reach is declared rather than assumed, and it should be treated as a controlled document: versioned, reviewed, and diffed on change. It is not, however, an authorization.
Where it comes from
Model Context Protocol; equivalent constructs in most agent frameworks.
Defining sources
- Model Context Protocol (MCP)Anthropic; open specificationOfficial text In the standards register
What it is not
These are routinely confused with Tool Manifest. The distinctions have consequences for how a system is governed.
- Authority Grant
A manifest says what the agent CAN reach. A grant says what it MAY commit, under whose authority, and up to what limit. Reading a manifest as a permission boundary is the most likely agentic governance error of the next two years.
- Agent Card
The manifest faces inward, toward the agent's own tools. The card faces outward, toward other agents.
How it connects
What it needs
- Tool Manifest depends on MCP Standard
- Tool Manifest is produced by Model Context Protocol Canon term
MARQUE questions it addresses
- AuthorityWhat is the agent permitted to commit, and who granted that?
Not to be confused with
- Authority Grant Canon term
Related framework objectives
Connected through the MARQUE (a reference framework organized around eight questions) crosswalk, an editorial mapping. These objectives from the Financial Services AI Risk Management Framework are assigned to the same questions that this term addresses. The ones sharing most of this term's vocabulary are shown first, as a reading aid. The assignment is to the question, not to the term: the source does not map this term to any objective directly.
Question: Authority · 39 control objectives assigned
- MP-2.1.2Assumptions and Limitations DocumentationMap
- MP-3.5.2Oversight Training and ResourcesMap
- MP-4.1.2Third-Party Resource DocumentationMap
Cite and reuse
Cite the identifier QIS-TERM-00006, not the URL: identifiers are stable, URLs may change. This entry is free to read, quote and index under the dual license. Corrections sent to editor@qisfund.com are published.
Technical details: identifier, graph relationships and record
| Predicate | Target identifier | Target | Predicate meaning |
|---|---|---|---|
dependsOn | std:mcp | MCP | The subject cannot function correctly without the object. |
notEquivalentTo | term:authority-grant | Authority Grant | The two are routinely conflated and are distinct. |
addresses | marque:authority | Authority | The subject speaks to the object as a question or concern. |
producedBy | term:mcp | Model Context Protocol | Read the other way round: the object produces the subject. The subject emits the object as an output. |
- Canonical identifier
QIS-TERM-00006- Tier
- Canonical industry term
- Domain · layer
- Capability · Intelligence
- Semantic aliases
- None recorded
- First published
- 2026-08-02
- Last reviewed
- 2026-08-02 · 180-day cycle