A stateless HTTP MCP server
Single tool with minimal definition quality. Tool name 'hello_world' lacks action verb (should be 'greet_user' or similar). Description is trivial (3 words, well below 10-char minimum for meaningful context). Parameter 'name' has no description despite being required for LLM understanding. No output schema documented. No error handling guidance. Fails baseline expectations for production-grade tools.
Hello world
Tool name lacks action verb. 'hello_world' does not convey intent; should start with verb like 'greet_', 'generate_greeting_', or 'send_greeting_'. LLMs infer tool purpose from name before reading description.
Tool description is trivial (3 words: 'Hello world'). Baseline is 34-392 chars; this provides zero context for when/why to call the tool. Must explain: what it does, when to use it, what it returns.
Parameter 'name' has no description (null in schema). LLMs cannot infer that this is a person's name vs. a system identifier. Must add: 'The person's name to greet (string, 1-100 chars).'
No output schema documented. LLMs need to know the return type and structure. Must document: returns a string greeting message.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 34 | 2026-07-28+ | v2 |
No error handling or recovery guidance. If 'name' is empty or contains invalid characters, tool should return actionable error (not a stack trace) and suggest correction.