An MCP server implementation using Axum HTTP framework with counter and calculator tools
Critical failures across naming, descriptions, and schemas. Tool names lack action verbs (sum, sub, increment, decrement, get_value, say_hello, echo). Descriptions are duplicated and misleading: 'sum' and 'sub' both claim to 'Calculate the sum of two numbers' (sub should say 'difference'). Parameter descriptions are sparse or null (tool 1 'b' param has null description). Duplicate tool names (sum appears twice, tools 1 and 8). No output schemas documented. No error handling guidance. Schemas present but incomplete, many params lack descriptions entirely. This server would fail code review.
Decrement the counter by 1
Repeat what you say
Get the current counter value
Increment the counter by 1
Say hello to the client
Calculate the sum of two numbers
Calculate the sum of two numbers
Calculate the sum of two numbers
Duplicate tool names: 'sum' appears twice (tools 1 and 8) with different schemas. LLMs cannot disambiguate which to call.
Misleading descriptions: 'sub' tool claims to 'Calculate the sum of two numbers' but should say 'difference'. Tool 1 'b' parameter has null description.
Missing action verbs in tool names. 'sum', 'sub', 'increment', 'decrement' lack clarity. Should be 'calculate_sum', 'calculate_difference', 'increment_counter', 'decrement_counter'.
No output schemas documented. LLMs cannot plan downstream calls or extract return values. Tools return JSON but structure is undocumented.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 36 | <=2025-11-25 | v2 |
No error handling guidance. If a tool fails, LLM has no recovery path. No categorization of retryable vs fatal errors.