Worked examples
Five real tool calls against the ATP MCP server, trimmed, with what came back and why.
These examples show what a caller sends and what the server returns. They are generated by the project's tests against counting fakes. Every identifier is fake and nothing is live data.
Not deployed
Local fakes only
The server is not deployed and has been tested locally against in-memory fakes only. Execution is gated off by default, and no application implements the adapter API yet. There has been no independent security review yet.
Each example has two parts you do not control. The server picks the application, the granted scopes and the operator gates from the verified token and its configuration. The tool arguments never select them. See Authorization. Results are shown as structuredContent, trimmed.
Benign canonical read
A caller with only atp:read reads an Atom. The call needs no backend.
{ "name": "atp_get_atom",
"arguments": { "chainId": 97,
"atomCore": "0xeeee...eeee",
"atomId": "0xaaaa...aaaa" } }{
"status": "FOUND",
"atom": { "state": "ACTIVE", "terminalOutcome": "NONE",
"completionMode": "ROOT_OR_DELEGATE",
"quantity": "1", "finalized": false },
"evidence": { "source": "ATP_CHAIN_READ", "chainId": 97,
"protocolVersion": "2.4.0",
"blockNumber": "1000000",
"finality": "FINALIZED", "runtimeVerified": true }
}Why: the server made one chain call and zero backend calls. The Atom facts come with finalized-block evidence, so you can tell which block the answer describes. This is an observation, not a permission. See ATP binding and chain reads.
Blocked unapproved write
A caller holds atp:read, atp:preflight and atp:execute. The execution gate is off for its application.
{ "name": "atp_request_authorized_execution",
"arguments": { "jobRef": "job-synthetic-0001",
"requestId": "req-synthetic-0001" } }{
"status": "ERROR",
"error": { "category": "BLOCKED_POLICY",
"reasonCode": "EXECUTION_DISABLED",
"retrySafe": false,
"correlationId": "corr-synthetic-0001" }
}Why: holding the scope is not enough. The operator must also list the application in ATP_MCP_EXECUTION_ENABLED_APPS. The server denied the call before any backend call, with zero chain calls. The result has isError: true.
Cross-tenant denial
A caller on the dashboard application asks for the attempt record of a job it may not see.
{ "name": "atp_get_execution_attempt",
"arguments": { "jobRef": "job-synthetic-other-tenant" } }{
"status": "ERROR",
"error": { "category": "FORBIDDEN",
"reasonCode": "REFERENCE_NOT_ACCESSIBLE",
"retrySafe": false,
"correlationId": "corr-synthetic-0001" }
}Why: the owning application decides whether a caller can see a job. The server asked the backend once and passed on a single FORBIDDEN. The answer is the same whether the job does not exist or belongs to someone else, so it leaks nothing about the other tenant.
Ambiguous execution
A caller with atp:execute requests execution. The backend call times out after it may have been received.
{ "name": "atp_request_authorized_execution",
"arguments": { "jobRef": "job-synthetic-0001",
"requestId": "req-synthetic-0001" } }{
"status": "ERROR",
"error": { "category": "RECONCILIATION_REQUIRED",
"reasonCode": "EXECUTION_OUTCOME_UNKNOWN",
"retrySafe": false,
"correlationId": "corr-synthetic-0001" }
}Why: the request may have reached the backend, so the outcome is unknown. A timeout does not prove nothing happened. The server made exactly one backend call and did not retry. Do not resend. Read the attempt and result for the same jobRef. See Preflight and execution.
Confirmed result with chain readback
A read-scoped caller asks for the result of a job.
{ "name": "atp_get_execution_result",
"arguments": { "jobRef": "job-synthetic-0001" } }{
"status": "OBSERVED",
"source": "APPLICATION_LEDGER",
"job": { "action": "PAY", "kind": "CONFIRMED",
"upstreamCode": "PAID",
"atomId": "0xaaaa...aaaa",
"observedAt": "2026-11-01T00:00:00Z" },
"chainReadback": {
"status": "ATOM_OBSERVED",
"atom": { "state": "FINALIZED", "terminalOutcome": "RELEASE",
"finalizationRoute": "BUYER_COMPLETION_DELEGATE",
"sellerShareBps": 10000 },
"evidence": { "chainId": 97, "finality": "FINALIZED",
"runtimeVerified": true }
}
}Why: the ledger's CONFIRMED is only a claim by the application. Because it came with an Atom id, the server also read that Atom from the chain. ATOM_OBSERVED is the canonical proof that the Atom exists at the finalized block. Had the Atom not been there, the status would be ATOM_NOT_OBSERVED_AT_FINALIZED_BLOCK and you should not treat the job as done.
Reading the pattern
| Example | Chain calls | Backend calls |
|---|---|---|
| Benign canonical read | 1 | 0 |
| Blocked unapproved write | 0 | 0 |
| Cross-tenant denial | 0 | 1 |
| Ambiguous execution | 0 | 1 |
| Confirmed result with readback | 1 | 1 |
Next, see the Tool reference for every field.