ACORN GLOBAL · ENGINEERING FIELD GUIDE · PROTOCOL INTEGRITY
Debug MCP tool call and integration failures
Tool discovery and tool execution are different operations. An advertised MCP tool is not proof that a request can complete.
Réparer les intégrations MCP — mesures vérifiables, aucune garantie ni résultat client inventé.
Look for these observable signals
- Tool discovery succeeds but an invocation fails
- Input schema and client arguments disagree
- Timeouts or transport errors are misreported as model errors
A REPRODUCIBLE METHOD
Four steps to a useful baseline
Inspect a public, credential-free tool descriptor and argument schema.
Reproduce the smallest failing tool call in an authorized test environment.
Classify transport, validation and application errors separately.
Verify a working readback; do not claim LIVE based on a manifest alone.
Evidence worth retaining
Tool name, redacted schema, authorized request ID, test timestamp and verified readback.
Limit: Never paste API keys or proprietary payloads into a public diagnostic. This guide does not test a third-party endpoint.
If required measurements are unavailable, record them as not measured. Never replace an unknown value with zero or claim a successful repair without a verified readback.