Model Context Protocol server for calendar and date utilities
Calendar MCP has 7 well-named tools with consistent verb-noun naming (get_*, calculate_*, is_*, days_*). All tools have documented input schemas with proper type definitions and descriptions. However, descriptions are notably brief (10-50 chars), falling below the 194-char baseline and pattern:tool-description guidance of 50-200 chars for LLM optimization. Parameter descriptions are minimal (10-20 chars), below the 72-char baseline. No output schemas are documented in the source code, the rubric explicitly requires output schema documentation (pattern:tool). Error handling is absent, no guidance on recovery strategies, validation failures, or actionable error messages. The domain is simple (date utilities), which partially mitigates missing error handling, but the descriptions need substantial expansion to match production baselines.
Add or subtract days from a date.
Calculate days between two dates.
Returns today's date and metadata.
Get day of week for a given date.
Returns ISO week number and year.
Returns Monday-Sunday range for a given date.
Check if two dates are in the same week.
Output schemas not documented. LLMs need to know what fields to expect in responses to plan downstream tool calls and extract data correctly.
Tool descriptions are too brief (10-50 chars). Baseline is 194 chars; pattern:tool-description recommends 50-200 chars for LLM optimization. Current descriptions lack context for tool selection and do not explain WHEN to use each tool or dependencies between tools.
Parameter descriptions are minimal (10-20 chars). Baseline is 72 chars. Example: 'Date in YYYY-MM-DD format' is bare format instruction; should explain WHEN to provide it and what the tool does with it.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 51 | 2026-07-28+ | v2 |
| 2026-03-09 | D | 52 | - | v1 |
No error handling or recovery guidance. Tools accept free-form date strings without validation; no guidance on what to do if parsing fails or if dates are invalid.
No tool inter-dependencies documented. For example, is_same_week depends on two dates being valid, and get_week_range could feed into subsequent calls. Dependencies should be hinted in descriptions.