An illustrative example of a minimal MCP server demonstrating tool registration and request handling
hello-mcp is a minimal illustrative example, not production-grade. Both tools have basic descriptions (10-30 chars, below the 50-200 char baseline for LLM-optimized descriptions). The 'echo' tool has a complete input schema with a required 'text' parameter; 'current_time' has an empty schema (no parameters). Neither tool has parameter descriptions, the schema lacks the 'description' field for the 'text' param. No output schemas are documented. Error handling is absent (no recovery guidance, no error classification). The code is pseudo-code with comments indicating the real SDK should be used. Tool definitions are visible and explicit, so no inference penalty applies.
Returns the current time in ISO 8601.
Returns the received text.
Descriptions are too short (10-30 chars) and lack LLM-optimized context. 'Returns the received text' and 'Returns the current time in ISO 8601' do not explain WHEN to use each tool or what downstream actions they enable.
Parameter 'text' in 'echo' tool has no description field in the schema. LLMs cannot infer what 'text' means or what format is expected.
No output schemas documented. LLMs do not know what fields to expect in responses, preventing downstream tool chaining and data extraction.
No error handling or recovery guidance. If 'echo' receives null or 'current_time' fails, the LLM has no actionable next step.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | 2026-07-28+ | v2 |
Code is pseudo-code with comments directing users to the official SDK. This is not a functional MCP server, it is a skeleton/template.