← Glossary
Glossary · AI and agent workflows
Tool contract
The written specification of one tool: purpose, inputs, output, errors, retry behavior, access and completion evidence.
The contract is what a tool's builder commits to and what a caller can test one call at a time. It does not make the tool behave and does not say when to use it; a procedure does that. Its access line is written twice: the intended scope, and the effective scope with its enforcer and that enforcer's documented coverage. A stated scope with no named enforcer is an intention, as the deprecated MCP roots feature was.