MCP is a communication mechanism for an agent to discover and invoke tools or access resources through defined interfaces. It standardizes tool discovery and invocation, but does not itself define business purpose, delegated authority, decision context, or evidence obligations. section 6.2.3 section 6.3
Treat MCP as one part of a governed interaction:
- Use the conversational contract to define why the agent acts, what constraints apply, what authority is delegated, and what evidence is required. section 6.2.3
- Expose bounded enterprise capabilities through an MCP server or gateway rather than granting direct access to underlying systems. section 6.3
- Enforce identity, scopes, business-purpose policy, validation, recovery, and evidence recording at invocation time. section 6.3
Quality investigation
An agent investigates whether manufacturing lot 2418 requires containment. MCP can expose the production-history tool, while the conversational contract restricts evidence sources and prohibits placing the lot on hold or contacting external parties. A valid tool call therefore remains insufficient if it exceeds delegated authority. section 6.2.3
Table 6.3 API, event, and conversational contracts
|
Contract type
|
Primary design concern
|
Typical contents
|
What it does not carry by itself
|
|
API contract
|
A callable operation’s request and response shape
|
Endpoint, method, request and response schemas, status
codes, authentication scheme
|
Runtime intent, delegated authority, decision context, and
evidence obligations
|
|
Event contract
|
A published fact, state change, or signal
|
Topic, event type, payload schema, producer, timestamp,
version
|
Why downstream action should occur, who owns the outcome,
and how causation is reconstructed
|
|
Conversational contract
|
The meaning and boundaries of an agentic interaction
|
Intent, context, constraints, authority, outcome, evidence
obligations
|
Transport mechanism, endpoint implementation, and full
payload schema
|
Compare API, event, and conversational contracts to see which interaction concerns MCP supports and which remain outside its scope. section 6.2.3




















