Here’s one I keep running into. An AI agent asks a tool to create a ticket. The tool calls the real API, the request times out, and now the tool has to tell the agent something, ideally the truth.
The truth is awkward. Until someone reads it back, that ticket is both created and not created, which is fine for cats and terrible for billing.
If the tool says “failed”, the agent does what any of us would and retries, and if the first request did land you now own two tickets. If it says “success”, it’s guessing with confidence, which is a career path but not a protocol. For most of these tools those are the only two words they know.
Some context: MCP servers are the wrappers agents use to call real APIs. We read the source of 100 popular ones that have write tools (read, not run). Of the 42 that wrap a web API, 39 have no way to say “I don’t know if that write happened”. Across all 100:
| What the write tool can report | Servers |
|---|
| Success or failure, machine-readable | 44 of 100 |
| “Outcome unknown”, machine-readable | 7 of 100 |
| A signal that the call is safe to repeat | 17 of 100 |
The irony is that most of the APIs underneath already have the pieces: ETags, idempotency keys, 409s. The wrappers drop them somewhere on the way to the agent.
We went with an explicit “unknown” result plus a hint about whether a retry is safe. The other way is to say “failed” and lean on idempotency keys, so a retry can’t double-write. Which would you pick for a caller that can’t walk over and ask someone?
Write-up with the full method and data: 100 MCP servers, what their writes report. I’m the author and I run IsoKron.