traintrack-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRAINTRACK_BASE_URL | No | TrainTrack deployment to use. http and https URLs are supported, including deployments under a path. | https://traintrack.stupidlabs.lol |
| TRAINTRACK_TIMEOUT_MS | No | Positive request timeout in milliseconds. | 30000 |
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 |
|---|---|
| search_trainsA | Search Indian Railways trains by name, number, or text. Upstream limit: 60 requests/minute; results may be cached for up to 12 hours. |
| get_train_infoA | Get a train's identity, endpoints, and available running instances. Upstream limit: 30 requests/minute; results may be cached for up to 30 minutes. |
| get_train_scheduleA | Get a train's scheduled stops, running days, times, and available station coordinates. Upstream limit: 20 requests/minute; results may be cached for up to 12 hours. |
| get_train_live_statusA | Get live station-by-station progress, delays, platforms, current reported position, and route geometry. Upstream limit: 12 requests/minute; live results may be cached for up to 45 seconds. |
| find_trains_between_stationsA | Find direct trains between two station codes, optionally sorted by fastest journey or earliest departure. Upstream limit: 20 requests/minute; results may be cached for up to 30 minutes. |
| get_train_exceptionsA | Get exceptional service information such as cancellations or diversions. Read the returned message field. Upstream limit: 20 requests/minute; results may be cached for up to 5 minutes. |
| get_pnr_statusA | Look up Indian Railways PNR booking, passenger, and chart status. PNR data is sensitive. Upstream limit: 2 requests/minute; PNR results are never stored in the result cache. |
| get_station_coordinatesA | Get the name and bundled map coordinates for an Indian Railways station code. Upstream limit: 120 requests/minute. |
| search_stationsA | Search bundled Indian Railways stations by code or name. Upstream limit: 120 requests/minute. |
| track_trainsA | Get live tracking for up to 10 trains in one request. Individual train failures are returned in the trains array. Upstream limit: 6 requests/minute; successful live results may be cached for up to 45 seconds. |
| check_traintrack_healthA | Check whether the public TrainTrack API is available. Upstream limit: 120 requests/minute. |
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 11 tools
Each tool serves a unique function, from searching trains and stations to live tracking and PNR status, with no apparent overlap in purpose.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_train_info, search_stations, check_traintrack_health), ensuring predictability.
With 11 tools, the set is well-scoped for an Indian Railways data API, covering essential operations without unnecessary redundancy.
Core functionalities like search, schedule, live status, PNR, and exceptions are covered. Minor gaps like fare or seat availability exist but are not critical for the api's purpose.