RailRoute journey planner

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Plan intercity journeys in India by train, flight or both, with a fare for every travel class.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "RailRoute journey planner": {
      "url": "https://www.railroute.in/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (8)

• find_place read-only

  Turn what somebody typed into RailRoute place ids. ALWAYS call this before plan_journey. A place is a city with all of its stations and airports — Mumbai covers CSMT, LTT, Dadar, Bandra Terminus and the airport — so the planner can choose the right terminal rather than making the traveller do it. Typing a station code ("CSMT") finds the city and says which terminal matched.

  Parameters:

  • query (required) — string — A city, station name or station code
  • limit — integer

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• plan_journey read-only

  Every practical way to get from one place to another: direct trains with their fares per class, journeys with one change of train, flights, mixed train-and-flight itineraries, and GOVERNMENT BUSES from the state road transport corporations, priced from their own reservation systems. This is the whole answer in one call. Place ids come from find_place. Use it for bus questions too. On a large share of the corridors these corporations serve there is no through train at all — Mysuru to Mangaluru runs twenty-five buses a day and not one direct train — so a journey this tool answers with a bus is often the only through service that exists, not a second-best. Pass `train_class` when the traveller has named one ("3A", "sleeper") and every train is priced in it; leave it out and each train is priced in every class we have evidence it carries. Pass `modes: "trains_only"` when they have said train — do not ask them to choose otherwise, because the point of this planner is that they do not have to. Pass `arrive_by: true` when they named a time they must BE somewhere rather than a time they want to leave.

  Parameters:

  • from (required) — string — Place id from find_place
  • to (required) — string — Place id from find_place
  • date (required) — string — Travel date in IST. Today is allowed; the past is refused.
  • limit — integer — How many of EACH kind to return. Raise it only if the traveller asks to see more.
  • modes — string — Restrict the answer. Default 'any' ranks trains, flights and government buses together — leave it out unless the traveller has actually named a mode. 'trains_only' and 'flights_only' both drop the buses.
  • quota — string
  • arrive_by — boolean — When true, `date` is the day they must ARRIVE, and journeys may depart the day before.
  • train_class — string — Price every train in this class: 2S Second Sitting, SL Sleeper, CC AC Chair Car, 3E AC 3 Economy, 3A AC 3 Tier, 2A AC 2 Tier, 1A First AC, EC Executive Chair Car. Omit to price each train in every class we know it carries.
  • ask_preferences — boolean — Whether to ask the traveller for a travel class when they have not named one. Set false for automated or bulk use.
  • include_connections — string — Journeys with one change of train. 'auto' searches for them when direct trains are thin, which is when they matter; 'always' searches regardless and costs a few more seconds.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• check_train_options read-only

  Live seat availability per class for one train on one date, plus every other way to book it when the through ticket will not confirm: a split at an intermediate station, boarding earlier, alighting later. This is the tool that rescues a waitlisted train. It spends a metered upstream call, so ask it about trains the traveller is actually considering rather than sweeping a list.

  Parameters:

  • train_number (required) — string
  • from (required) — string — Station code the traveller boards at
  • to (required) — string — Station code the traveller alights at
  • date (required) — string
  • quota — string
  • include_rac — boolean — RAC is a ticket that carries a right to board, so it counts as bookable by default.

  Hints: read-only yes · destructive not declared · idempotent no · open-world yes

• train_schedule read-only

  Every stop of one train with its scheduled arrival and departure, in order. Scheduled times only — this says nothing about where the train is today.

  Parameters:

  • train_number (required) — string

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• station_departures read-only

  Every train scheduled to call at a station, in departure order — the enquiry board, not a journey plan. Use plan_journey when somebody wants to get somewhere; use this when they are asking what leaves from here. Scheduled times only.

  Parameters:

  • station_code (required) — string — Station code, e.g. CNB
  • after — string — Only departures at or after this IST clock time, HH:MM
  • limit — integer

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• journey_calendar read-only

  Day-by-day service over a span of dates for a station pair: which days have a direct train and which have none, plus the weekly pattern. Use this when somebody is flexible about when they travel, or asks 'does it run on Sundays'. Timetable only — it says nothing about seats.

  Parameters:

  • from (required) — string — Origin station code
  • to (required) — string — Destination station code
  • start_date (required) — string — First day of the span
  • days — integer

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• nearby_stations read-only

  Other railway stations within a radius of one station, nearest first. Useful when a place has no service of its own and the traveller needs to know what is reachable — the planner already does this internally, so reach for it only when somebody asks the question directly.

  Parameters:

  • station_code (required) — string
  • limit — integer
  • radius_km — integer

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• next_confirmed_date read-only

  Search forward up to a month for the first date this route can actually be travelled with a confirmed berth — direct trains and one-change journeys together. Use it when a traveller is flexible about WHEN and the date they asked for is waitlisted. EXPENSIVE: it checks seats across dozens of trains and dates, so it is limited to a few calls an hour; for a single date use check_train_options instead.

  Parameters:

  • from (required) — string — Origin station code
  • to (required) — string — Destination station code
  • date (required) — string — The date to search forward FROM
  • quota — string

  Hints: read-only yes · destructive not declared · idempotent no · open-world yes

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.