Loading ToolBench
Ruby-based MCP server that exposes Foobara commands as MCP tools via stdio transport
This MCP server has fundamental quality issues that make it unsuitable for production use. Of 6 tools, 5 have parameter descriptions explicitly set to `null` in their JSON schemas, making parameter meaning completely opaque to LLMs. Tool descriptions exist but are minimal (8-31 characters), below the 10-character minimum and well below the 50-200 character baseline for LLM-optimized tools. No error handling guidance, no output schemas documented, and no parameter validation hints. The server demonstrates basic schema structure but lacks the documentation depth required for reliable agent tool selection and execution.
Computes an exponent
Parameter descriptions are explicitly null (5 of 6 tools). LLMs cannot infer parameter meaning from names alone. 'base', 'exponent', 'seed', 'name', 'year_of_birth', 'id' are passed to the agent without any context about expected values, ranges, or formats.
5 of 6 tools lack descriptions or have descriptions under 20 characters (minimum baseline). Examples: BuildSuperDuperSecret (no description), FindAllCapybaras (no description). Tool descriptions must be 50-200 characters to guide LLM selection.
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields. ComputeExponent returns an integer but provides no context; CreateCapybara and UpdateCapybara return Capybara objects but structure is not exposed to the LLM.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 28 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 20 | 2025-03-26+ | v1 |
No error handling guidance. Tools provide no recovery hints for common failure cases (e.g., 'UpdateCapybara with invalid id should suggest calling FindAllCapybaras first'). Agents cannot self-correct on errors.
Naming convention issues. 'SomeOrg::SomeDomain::ComputeExponent' uses full namespace in tool name (not idiomatic MCP). 'BuildSuperDuperSecret' does not follow verb_noun pattern clearly. 'Foobara::McpConnector::Commands::Initialize' exposes internal class hierarchy and is overly verbose.
UpdateCapybara has parameters without descriptions and missing required field validation hint. The 'id' parameter is required, but 'name' and 'year_of_birth' are optional, no description explains when partial updates are valid or what happens if both are omitted.