IRCTC MCP has 7 tools with basic Zod schemas and descriptions, but significant gaps prevent production readiness. All tools have descriptions (10-60 chars, below the 50-200 char LLM-optimized baseline) and input schemas with type definitions. However, output schemas are completely undocumented, LLMs cannot plan downstream calls or extract structured data. Parameter descriptions are minimal (e.g., 'Train number' lacks format/range guidance). No error handling guidance, no recovery paths, and no indication of which tools are idempotent or safe to retry. Tool names follow verb_noun convention (good), but descriptions lack WHEN/WHY context. The server lacks pagination support despite searchTrains and checkSeatAvailability likely returning large result sets. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being READ_ONLY.
Check if the chart has been prepared for a PNR
Check seat availability for a specific train and journey details
Get live status of a running train
Get booking history for a PNR
Get the current status of a PNR (Passenger Name Record)
Get the complete schedule of a train
Search for trains between two stations on a specific date
Output schemas completely undocumented. No tool returns a documented schema, LLMs cannot infer what fields to expect, breaking downstream tool chaining and data extraction.
Descriptions are too short (10-60 chars vs. 50-200 char LLM-optimized baseline). Missing WHEN/WHY context. E.g., 'Get the current status of a PNR' lacks guidance on when to call this vs. getPnrHistory or checkPnrChartStatus.
Parameter descriptions lack format/range constraints. 'Train number' does not specify format (e.g., 5-6 digits). 'Date in YYYY-MM-DD format' is stated but not enforced via regex or validation. LLMs cannot self-correct invalid input.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | 2026-07-28+ | v2 |
No pagination support. searchTrains and checkSeatAvailability likely return large result sets but lack limit/offset/page parameters. Large responses blow context windows and waste tokens.
No error handling guidance. getPnrHistory returns a placeholder error ('This feature is not yet implemented') with no recovery path. No tool documents retryable vs. fatal errors or suggests next steps on failure.