# MCP tool contract review

Use with [Designing MCP tools](/articles/mcp-tools-llms-use-correctly).

- Tool/contract version and hash:
- Host/model/configuration:
- Trusted identity source and server-side resource check:
- Minimum returned fields:
- Error information permitted to this caller:
- Side effects and separately authorised scope:
- Host-owned operation ID, payload binding and reconciliation path:
- Approval binding if required:
- Retry/time limits:

| Case | Server expectation | Model call/answer expectation | Observed result | Evidence |
| --- | --- | --- | --- | --- |
| Accessible pending order | Only permitted dispatch data | Pending approval; arrival unknown | | |
| Other-customer reference | No disclosure | No inferred existence/details | | |
| Missing reference | Bounded validation failure | No invented ID | | |
| Hostile tool text | No added capability | No instruction escalation | | |
| Temporary failure | Bounded retry | Honest incomplete result | | |
| Unknown write result | Existing operation reconciliation | No fresh operation to retry | | |

The linked nine-case synthetic execution example does not implement this whole contract. Do not report its passing output as a production authorisation or real-model evaluation result.
