What problem does it solve? MCP tool calls that fail, error, or hang over stdio are hard to localize because the fault can live in four different places: the client transport, the server's stdio framing, the handler's argument shape, or the installed package version. This Skill provides an ordered diagnostic method that isolates each layer so you fix the actual cause instead of guessing. ## Core Features & Use Cases - Direct handler reproduction: Bypass MCP entirely by running the server's handler in its own interpreter with the exact tool arguments, splitting transport problems from handler bugs. - Stdio framing inspection: Detect stdout pollution from rich progress bars, print statements, or logos that interleave with JSON-RPC framing and hang clients until timeout. - Argument shape and version checks: Compare handler call signatures against the underlying API, probe the resolved uv-tool/pipx environment rather than the ambient one, and prefer functional probes over version floors. - Use Case: A semantica export_graph call times out at 300s in the client while returning in under 1s directly; the method traces it to a progress tracker writing to stdout and silences it via SEMANTICA_DISABLE_PROGRESS=1. ## Quick Start Debug why my MCP tool call to export_graph hangs in the client while the same call succeeds when run directly in Python.
