Loading ToolBench
This is an intentionally minimal reference server for learning MCP concepts. It contains only 1 tool: 'hello'. The tool has a trivial implementation with no input parameters and a hard-coded response. The tool description is present but extremely generic (11 words). There is no input schema visible, the tool is registered with an empty object `{}` as its input definition. The server demonstrates correct HTTP/SSE/STDIO transport setup but provides no meaningful tool definitions suitable for production use. The 'hello' tool does not accept parameters, provide structured output documentation, or implement any error handling. This is by design, it's a learning example, not a production-grade server.
Returns a hello world message
Tool 'hello' has NO input schema. Registration shows empty object `{}` with no type definitions, properties, or constraints.
Tool name 'hello' does not follow verb_noun convention. 'hello' is a noun/greeting, not an action verb (get_, create_, list_, search_, etc.). LLMs expect action verbs to infer intent.
Tool description 'Returns a hello world message' is only 33 characters and provides no context for WHEN to use it or WHAT it does beyond a trivial demo. No parameter descriptions exist.
No output schema is documented. LLMs cannot determine what fields the response contains or how to extract values for downstream tool calls.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 30 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 0 | - | v1 |
No error handling or recovery guidance. The tool returns a hard-coded success; no error cases, validation, or actionable error messages are present.