Simple MCP server using FastMCP to add two numbers - Containerized version
Single tool with basic definition. Tool name is clear and verb-based (add_numbers). Description is present but minimal (15 characters: 'Add two numbers together.'). Input schema is properly typed with float parameters, but parameter descriptions are generic and somewhat awkward ('First number to addition', 'Second number to addition', awkward phrasing). No output schema documented. No error handling guidance. No tool annotations or safety hints. Follows basic tool definition structure but falls short of production-grade polish expected by pattern:tool and pattern:tool-description.
Add two numbers together.
Tool description is extremely brief (15 chars), below the 34-char p10 baseline for production tools. Lacks WHEN/WHY context for LLM selection.
Parameter descriptions contain awkward phrasing ('First number to addition' should be 'First number to add'). Descriptions do not follow pattern:tool-description's guidance: no range constraints, no format hints, no dependency notes.
No output schema documented. Tool returns a float, but no schema description tells the LLM what to expect or how to use the result in downstream calls.
No error handling guidance. Tool lacks recovery patterns (pattern:recovery-guide): no error messages guide the LLM on what to do if inputs are invalid or operation fails.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 53 | 2026-07-28+ | v2 |
| 2026-03-09 | D | 57 | - | v1 |
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). The tool is read-only and idempotent, but these hints are absent from the definition, forcing the LLM to infer safety properties.