A Model Context Protocol server that provides Chinese holidays data including name, date, days, and working days for a given year
Single tool with basic schema and minimal description. Tool name 'get_chinese_holidays' follows verb_noun convention (+), but description is only 34 chars, below the 50-char baseline for clarity. Input schema present with proper type and required fields, but lacks parameter constraints (e.g., year range, format). No output schema documented. No error recovery guidance. Tool does one thing (read-only), but lacks the depth expected for production use.
Get chinese holidays data for a year
Tool description too brief (34 chars). Lacks WHEN to use, WHAT it returns, and any prerequisites. LLMs cannot determine selection criteria.
No output schema documented. LLMs cannot plan downstream operations or extract required fields (e.g., holiday names, dates, day counts).
Year parameter lacks constraints. No min/max bounds, no format guidance. LLMs may pass invalid years (e.g., 1000, 9999) without validation.
Error handling returns raw API errors without recovery guidance. 'API error: ...' tells LLM nothing about retry eligibility or next steps.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2026-07-28+ | v2 |
Resource handler hardcoded to DEFAULT_YEAR (2025). ListResources returns only one static resource; ReadResource ignores year parameter in URI. Inconsistent with tool flexibility.