A simple MCP server demonstrating ping-pong command handling with session management, supporting both FastAPI and SSE transports
Single tool 'ping-pong' has a name that violates verb-first conventions and lacks action clarity. Description is present but minimal (29 chars). Input schema is visible with two parameters (command, session_id), both typed as strings with basic descriptions. However, the command parameter accepts free-form strings instead of enums, inviting hallucinated values. No output schema is documented. The tool's purpose and return type are ambiguous to an LLM. No error handling guidance provided. Session ID as a parameter is a protocol anti-pattern (MCP uses stateless request handling). Overall, this is a minimal implementation lacking depth across all quality dimensions.
MCP handler for ping-pong commands
Tool name 'ping-pong' does not follow verb-first convention. Should be 'send_ping', 'execute_ping', or similar action-oriented name.
Description is only 29 characters: 'MCP handler for ping-pong commands'. Too brief to guide LLM selection. Does not explain what the tool does, when to use it, what happens, or what it returns.
Parameter 'command' accepts free-form strings (ping|pong|count) but is declared as type string with no enum constraint. LLMs will hallucinate invalid command values; tool silently returns 'unknown command' instead of guiding recovery.
No output schema documented. Tool returns a string, but LLM cannot predict structure or parse responses reliably. For 'count' command, numeric vs string ambiguous.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 32 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 19 | - | v1 |
Parameter 'session_id' exposed to client as a tool input. MCP protocol is stateless; session tracking should be handled server-side via per-request _meta, not as a tool parameter. This anti-pattern couples the tool interface to session management.
Error handling returns generic exception strings (e.g., 'unknown command') without guiding the LLM on valid options or recovery steps. No actionable error messages per pattern:recovery-guide.