No user-submitted related servers found.
Scored across 1 tool
The server exposes exactly one top-level tool (run_python), so there is no possibility of misselecting between tools. The internal async functions (add, echo, fail, big, slow, wipe) are clearly documented as stubs of the wrapped server rather than separate selectable tools, keeping the surface unambiguous.
With a single tool, there is no cross-tool naming inconsistency, and the name run_python follows a clear verb_noun snake_case pattern. The wrapped stubs also use consistent lowercase/snake_case identifiers and are dispatched via a uniform params-dict convention.
One tool is deliberately minimal and is exactly the point of a code-mode server: a single sandbox gateway replaces a large tool surface. It earns its place and is not trivial, though a single-tool surface is unconventional and offers no alternative entry point if the sandbox is unsuitable.
For the stated purpose (sandboxed Python execution with access to wrapped tools), the surface is effectively complete—any computation or tool invocation is expressible in code. Minor gaps: no separate tool-discovery or state-management tool outside search_tools described in prose, and the wrapped stubs are clearly a test fixture rather than a real domain surface.