Model Context Protocol (MCP) server for X Y Z
Single tool 'add_two_numbers' has critical definition gaps. Tool name lacks action verb clarity (should be 'sum_numbers' or 'calculate_sum'). Description is minimal (12 chars, below 20-char threshold). Input parameters 'a' and 'b' have null descriptions, violates requirement that every parameter must have a non-empty description. No output schema documented. No error handling guidance. Zod schema present but parameter descriptions missing entirely in the tool registration.
Add two numbers
Parameter descriptions are null/missing. Input schema shows {"a":{"type":"number","description":null},"b":{"type":"number","description":null}}. LLMs cannot infer what 'a' and 'b' represent without descriptions.
Tool description 'Add two numbers' is 12 characters, below 20-char minimum. Lacks context for when/why to use this tool, what it returns, or any prerequisites. Does not answer: What does it do? When should the LLM call it?
Tool name 'add_two_numbers' does not start with a clear action verb. 'add' is weak; 'sum', 'calculate', or 'compute' would be clearer. Name should convey intent before LLM reads description.
No output schema documented. Tool returns {content: [{type: 'text', text: string}]} but LLM has no formal schema to understand the response structure or plan downstream calls.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 30 | 2026-07-28+ | v2 |
No error handling or recovery guidance. If inputs are invalid (non-numeric, NaN, Infinity), tool provides no actionable error message to guide LLM retry or correction.