Loading ToolBench
MCP server running on Vercel with Next.js, using SSE transport and Redis for session management
Single tool 'echo' with critical definition gaps. Tool has a name but lacks meaningful description (null parameter description). Input schema present but minimal. No output schema documented. No error handling guidance. Tool is trivial (echo message) and does not reflect production-grade patterns. Naming is generic and does not follow verb_noun convention clearly. Parameter descriptions are null, violating the requirement that every parameter must have a description.
Echo a message
Parameter 'message' has null description. Every parameter must have a non-empty description explaining what it controls.
Tool description 'Echo a message' is too generic (14 chars). Descriptions must be 10 - 1024 chars and explain WHAT the tool does, WHEN to use it, and any prerequisites. Current description lacks context for LLM selection.
No output schema documented. LLMs cannot plan downstream calls or extract data without knowing what fields to expect.
No error handling guidance. Tool does not indicate what happens on failure, whether errors are retryable, or what the LLM should do next.
Tool name 'echo' is generic and does not follow verb_noun convention. Names like 'send_message', 'log_message', or 'repeat_text' would be clearer for LLM intent inference.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 36 | 2026-07-28+ | v2 |