irctc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IRCTC_PROVIDER | No | Provider selection: auto, confirmtkt, erail, rapidapi, mock | auto |
| IRCTC_TIMEOUT_MS | No | Per-request timeout in milliseconds | 15000 |
| IRCTC_RAPIDAPI_KEY | No | Optional RapidAPI key to add a keyed source at the front of the chain | |
| IRCTC_RAPIDAPI_HOST | No | Alternate RapidAPI listing host | irctc1.p.rapidapi.com |
| IRCTC_OFFLINE_FALLBACK | No | Append the offline estimator as a last resort (true/false) | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_stationsA | Find Indian Railways stations by name or code. Use this first when the user names a city rather than a station code, since most other tools need codes. |
| find_trains_between_stationsA | List direct trains connecting two stations on a given date, with departure, arrival, duration and available classes. Station names are accepted and resolved automatically. |
| get_train_scheduleB | Full stop-by-stop schedule for a train number: arrival, departure, halt, distance, day and platform, plus the days of the week it runs. |
| check_seat_availabilityA | Seat or berth availability for one train, class and quota on a date. Returns the railway status string (AVAILABLE / RAC / WL / REGRET) and, where known, a confirmation estimate. |
| get_fareA | Itemised fare for a train, class and quota between two stations: base fare, reservation and superfast charges, catering, dynamic surcharge and GST. |
| get_pnr_statusA | Current status of a 10 digit PNR: train, journey date, route, class and per-passenger booking and current status (CNF / RAC / WL) with coach and berth. |
| plan_journeyA | One-shot journey planner: finds trains between two stations on a date, then checks availability and fares for the preferred classes and ranks the options. Use this instead of chaining the individual tools when the user asks how to get from A to B. |
| list_reference_dataA | Reference list of Indian Railways travel class codes and booking quota codes, for interpreting or constructing other tool calls. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan_trip | Walk through planning a train journey: resolve stations, compare trains, check availability and fares, and recommend an option. |
| check_my_booking | Look up a PNR and explain what the status means in plain language. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| stations | Bundled directory of major Indian Railways stations with codes, states and zones. |
| trains | Bundled sample of popular trains with route, classes and days of operation. |
| reference | Travel class codes and booking quota codes used across the tools. |
TDQS
Scored across 8 tools
Most tools target distinct resources, but there is overlap between search_stations and find_trains_between_stations since both can accept station names, and plan_journey subsumes find_trains plus availability/fare. Descriptions mitigate this somewhat by clarifying intended use, but an agent could still misselect.
All tools follow a consistent snake_case verb_noun pattern (search_stations, get_fare, list_reference_data, etc.). Even longer names like find_trains_between_stations remain predictable and readable.
Eight tools is well within the ideal range and matches the server's scope of Indian Railways information and journey planning. No tool feels redundant or excessive; each covers a distinct aspect of the travel workflow.
The surface covers the core journey-planning lifecycle: station lookup, trains, schedule, availability, fare, PNR status, and a reference list. Minor gaps exist, such as live train running status and connecting-route discovery, but these are workaround-able and not critical for the apparent purpose.