A simple MCP server that echoes text messages
Single tool 'list-events' has critical definition gaps. Tool name lacks clarity (should be 'list_calendar_events' per verb_noun convention). Description is present but minimal (58 chars, below 100-char baseline for discovery). Input schema uses Zod with basic string types but lacks format constraints, ranges, or examples. No output schema documented. Parameters lack descriptions explaining expected date format (ISO 8601? locale-specific?). No error handling guidance. Tool does not follow pattern:tool-description or pattern:constrained-input standards.
Lists events for a given time period in the user's primary calendar
Tool name 'list-events' uses kebab-case instead of verb_noun convention. Should be 'list_calendar_events' to clarify scope and match LLM parsing expectations.
Input parameters 'startDate' and 'endDate' lack descriptions. LLMs cannot infer expected format (ISO 8601? RFC 3339? locale-specific?). No constraints on date ranges or validation rules.
No output schema documented. Response structure is hardcoded as text content; LLMs cannot parse event fields (start, summary, description) for downstream chaining or extraction.
Tool description (58 chars) is below baseline (100+ chars). Does not explain WHEN to use this tool, what it returns, or how to interpret results. Missing dependency hints (e.g., 'Returns up to 10 events; use pagination for larger ranges').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 34 | 2026-07-28+ | v2 |
Error handling returns raw error messages without recovery guidance. 'Erreur: {error.message}' in French does not tell LLM what to do next (retry? ask user? check credentials?).