A NestJS-based MCP server with SSE transport, tools, resources, and comprehensive testing setup
Single tool (hello-world) with basic implementation. Tool has a description and input schema present, but falls short on several quality dimensions: parameter description is minimal (10 chars: 'The name'), no output schema documented, no error handling guidance, and missing advanced features like tool annotations or idempotent hints. The naming is generic ('hello-world') and doesn't follow verb_noun convention (would be better as 'greet_person'). No validation rules documented for the 'name' parameter despite claiming 'letters and spaces only' in the description, this constraint is stated in tool description but not enforced via schema or returned in actionable error messages.
Returns a personalized greeting with progress tracking. Supports names with letters and spaces only.
Tool naming does not follow verb_noun convention. 'hello-world' is generic and does not convey the action (greeting). Should be 'greet_person' or similar action-oriented verb_noun pattern.
Input parameter 'name' has minimal description ('The name of the person to greet' = 38 chars). While present, it lacks actionable constraints. The tool description claims 'letters and spaces only' but this is not enforced via JSON Schema pattern or minLength/maxLength, and error messages will not guide LLM on what was invalid.
No documented output schema. LLMs cannot infer what fields the response contains or plan downstream calls. Progress tracking is mentioned in the tool description but response structure is not documented.
No error handling or recovery guidance. If LLM passes invalid input (e.g., numbers or special characters), there is no documented error response format or guidance on what to do next.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 41 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 32 | - | v1 |
No tool annotations present. Tool is marked READ_ONLY in risk field but does not use MCP toolAnnotations (readOnlyHint, idempotentHint, destructiveHint) for machine-readable declaration.