A simple MCP server that reverses strings
Single tool with minimal definition quality. Tool name 'string-reverse' lacks action verb prefix (should be 'reverse_string'). Description is adequate at 24 chars but generic. Input schema is present with type and constraint (minLength=1) but lacks depth. No output schema documented. No error handling guidance. No parameter relationship documentation. Composition is trivial (single tool, no chaining). Overall definition follows basic MCP structure but falls short of production patterns.
Reverse a given string
Tool name does not start with action verb. 'string-reverse' should be 'reverse_string' to match verb_noun convention and improve LLM intent parsing.
No output schema documented. LLMs cannot plan downstream operations or validate response structure. Should document that output is {content: [{type: 'text', text: string}]}.
No error handling guidance. Tool does not document what happens on empty string (minLength=1 prevents it) or edge cases. No recovery hints for LLM.
Description is generic and lacks context. Does not explain WHEN to use this tool or what the LLM should expect. Should be 50-200 chars with use-case guidance.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | 2026-07-28+ | v2 |
Input parameter 'input' is poorly named. Should be 'text' or 'string' to match semantic intent. Generic 'input' forces LLMs to infer meaning.