Loading ToolBench
Elevate stdio MCP servers into authenticated HTTP endpoints — self-hosted control plane.
The 'ping' tool is minimally defined. It has a trivial description ('Returns 'pong', a simple test tool.') that is only 44 characters and provides no actionable context for LLM selection. The input schema is empty ({}), which is appropriate for a no-argument tool, but the tool itself is a test fixture, not a production tool. The server appears to be a control plane/proxy for elevating stdio MCP servers, not an MCP server itself with meaningful tools. The single tool is defined in a test file (backend/tests/stdio_server_fixture.py), not in production code, indicating this is not a functional MCP server ready for evaluation.
Returns 'pong' — a simple test tool.
Tool defined in test fixture, not production code. The 'ping' tool is located in backend/tests/stdio_server_fixture.py, suggesting it is a test helper, not a real MCP server tool.
Description is trivial (44 chars) and lacks context. 'Returns 'pong', a simple test tool.' does not explain when to use it, what it does beyond echoing, or why an LLM would select it. Minimum 50-100 chars recommended for clarity.
No output schema documented. The tool description does not specify what the response structure is (e.g., {"message": "pong"} vs plain string). LLMs cannot plan downstream actions without knowing the response format.
Server is a control plane/proxy, not a functional MCP server. The codebase is a FastAPI application that elevates stdio MCP servers into HTTP endpoints. It is not itself an MCP server with meaningful tools for agent use.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | 2025-06-18+ | v2 |