Loading ToolBench
A simple hello world MCP server demonstrating basic tool functionality
The 'hello_world' tool lacks essential documentation and structure. It has no input parameters (empty schema), an extremely brief description (19 chars), and no output schema documentation. The tool is so trivial it provides no real value for evaluation, but from a quality standpoint it violates multiple critical MCP patterns: tool descriptions should be 10-1024 chars and contextual (this barely meets minimum length), parameter descriptions are required (none exist because there are no parameters documented), and output schema must be documented (missing entirely). This is a minimal 'hello world' demo server, not a production-grade MCP tool.
Hello World from tool
No input schema defined. Tool has empty input object {} with no parameter descriptions or type constraints.
Description is too minimal (19 chars). While technically above the 10-char floor, it provides no context about WHEN to use the tool, WHAT it returns, or ANY downstream expectations. LLMs cannot reason effectively with such sparse documentation.
No output schema documented. Callers have no structured expectation of what fields or format the response contains. This prevents downstream tool chaining and forces LLMs to infer structure.
Tool name 'hello_world' uses an underscore convention but does not start with an action verb (get_, create_, search_, list_, etc.). This violates the verb_noun naming pattern; 'get_greeting' or 'echo_message' would be clearer action-oriented names.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 28 | 2026-07-28+ | v2 |