Loading ToolBench
A gRPC transport implementation for the Model Context Protocol (MCP) that carries opaque JSON-RPC messages over a single gRPC bidirectional stream
Single tool 'echo' with minimal definition. Input schema present but description is trivial (11 chars, below 20-char threshold). No output schema documented. Tool is READ_ONLY but description does not explain what the tool does, when to use it, or what it returns. No parameter descriptions beyond the bare type. This is a proof-of-concept example, not production-grade tooling.
Echoes back the provided text.
Description is 11 characters ('Echoes back the provided text.'), below 20-char minimum.
No output schema documented. LLM cannot infer what 'echo' returns (string? object? array?). Violates pattern:tool requirement for documented return types.
Parameter 'text' has type but no description explaining its purpose, constraints, or format. Baseline: 100% of A+ tools have parameter descriptions.
Tool name 'echo' does not follow verb_noun convention (e.g., 'echo_text' or 'repeat_text'). Generic names reduce LLM clarity when multiple tools are available.
No error handling guidance. If 'text' is empty or oversized, what happens? LLM has no recovery path documented.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 33 | 2026-07-28+ | v2 |