irctc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IRCTC_API_KEY | No | Your secret API key from irctc.dev. If omitted, checks ~/.irctc/config.json or uses anonymous free daily quota. | null |
| IRCTC_API_BASE_URL | No | Production Rail Engine Gateway. | https://api.irctc.dev |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_pnrA | Check real-time Indian Railways PNR status, passenger manifest, coach & berth allocations (e.g. S4 65 LOWER BERTH), confirmation probability, and chart preparation status. |
| get_live_running_statusA | Get real-time live running GPS status of any Indian Railways train, including current delay in minutes, last crossed station, upcoming halts, platform numbers, and estimated arrival/departure times. |
| search_trainsA | Search running trains between any two Indian Railways station codes with departure/arrival times, travel duration, distance in kilometers, running days, and base fare estimates. |
| check_seat_availabilityA | Fetch official 14-day continuous seat availability calendar forecast across travel classes (1A, 2A, 3A, 3E, SL) and quotas (GN, TQ, PT, LD) directly from PRS. |
| get_vacant_berths_post_chartB | Find real-time vacant berths and seats after chart preparation from online reservation charts for Current Booking and TTE allocation onboard. |
| get_train_fareA | Calculate official IRCTC train fare breakdown across travel classes (1A, 2A, 3A, 3E, SL, CC, 2S) and quotas between origin and destination stations. |
| get_train_scheduleA | Get full train route schedule, intermediate halt stations, arrival/departure timings, stop durations, and total distance in km. |
| get_train_by_numberA | Get quick train basic details by train number, including official train name, train type, origin, destination, running days, and total distance. |
| search_trains_by_nameA | Search Indian Railways trains by train name query (partial match, e.g. "Rajdhani", "Shatabdi", "Vande Bharat", "Garib Rath"). |
| get_station_timetableA | Get all trains passing through, arriving at, or departing from a station on a given date (station timetable / arrivals & departures board). |
| search_stationsA | Autocomplete search Indian Railways stations by station code or partial city name (e.g. "NDLS", "delhi", "patna"). |
| get_station_by_codeB | Get detailed station information by station code, including station name, state, and railway division. |
| get_cancelled_trainsA | Get real-time list of today's cancelled, fully cancelled, and partially cancelled Indian Railways trains. |
| get_engine_healthA | Check irctc.dev Rail Engine health, offline corpus status, and in-memory index performance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool targets a clearly distinct railway query: PNR status, train details, live running, route search, seat availability, vacant berths, fare, schedule, station timetable, station lookup, cancellations, and engine health. The few superficially similar tools (search_trains vs. search_trains_by_name, get_train_by_number vs. get_train_schedule) are cleanly separated by their descriptions.
All names use consistent snake_case with a clear verb prefix (check_, get_, search_) followed by the resource or action. No mixed casing or conflicting verb styles appear across the set.
With 14 tools, the server stays within a well-scoped range for an Indian Railways information service. Each tool covers a distinct query type and none appear redundant or unnecessary.
The surface covers most core railway inquiry workflows: PNR, train search, schedules, live status, fares, availability, station data, and cancellations. Minor gaps exist for adjacent cases like rescheduled/diverted trains or booking-related actions, but the core informational lifecycle is strong.