MCP server for querying China Railway (12306) train tickets
Single tool 'search' has a clear action verb and basic schema with Zod validation. However, the description is minimal (11 chars in Chinese: '查询12306火车票'), falling well below the 10-1024 character guideline and providing no context for when/why to use it. Parameter descriptions are present but terse (e.g., '出发城市' = 'departure city' with no format guidance). No output schema is documented, the tool returns JSON-stringified text without specifying field structure, making it impossible for LLMs to plan downstream operations. Error handling returns raw exception messages without recovery guidance. The tool is READ_ONLY but lacks explicit idempotentHint annotation.
查询12306火车票
Tool description is only 11 characters (Chinese: '查询12306火车票'). Baseline is 10 - 1024 chars; descriptions under 20 chars score ≤40. Lacks context for LLM selection.
Output schema is not documented. Tool returns JSON-stringified text without declaring field structure (e.g., 车次, 出发站, 到达站, etc.). LLMs cannot extract or chain results.
Parameter descriptions are minimal and lack format/constraint guidance. 'date' has format='date' but no example or validation range. 'fromCity' and 'toCity' lack hints on accepted formats (city name vs code).
Error handling returns raw exception messages (e.g., '日期需为0~15天内', '没有找到出发城市') without recovery guidance. LLMs cannot determine if error is retryable or user-fixable.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | 2026-07-28+ | v2 |
Tool is READ_ONLY but lacks explicit toolAnnotations (readOnlyHint). Current spec (2026-07-28) expects structured tool annotations for agent planning.