Skip to main content
Glama

Find IRCTC railway retiring rooms

find_retiring_rooms
Read-onlyIdempotent

Locate IRCTC retiring rooms and dormitories at Indian Railways stations by station code, place, coordinates, or airport; get booking rules, price ranges, and portal link.

Instructions

Lists Indian Railways stations that have IRCTC retiring rooms (rooms and dormitories inside the station for ticketed passengers), at a station code or within a radius of a place. Returns station code, name, operator and distance, the booking rules, indicative price ranges and the IRCTC booking portal link. Live availability and exact prices are not available here: they need a Confirmed or RAC PNR on the IRCTC portal.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_retiring_rooms"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude (India). Use with lng.
lngNoLongitude (India). Use with lat.
iataNoIndian airport IATA code, e.g. DEL.
placeNoPlace name, e.g. 'Taj Mahal' or 'Paharganj, Delhi'; resolved to its best match.
radius_kmNoSearch radius when not giving a station_code.
station_codeNoIndian Railways station code, e.g. NDLS.

Output Schema

NameRequiredDescriptionDefault
notesYesData source and search caveats.
rulesYesIRCTC booking rules for retiring rooms.
stationsYesStations with IRCTC retiring rooms, nearest first.
booking_urlYesIRCTC retiring-room booking portal.
indicative_pricesYesTypical price ranges from secondary sources; not live.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.3.0
    • addedOutput schema / properties / booking_url / description
      Added value: +"IRCTC retiring-room booking portal."
    • addedOutput schema / properties / indicative_prices / description
      Added value: +"Typical price ranges from secondary sources; not live."
    • addedOutput schema / properties / notes / description
      Added value: +"Data source and search caveats."
    • addedOutput schema / properties / rules / description
      Added value: +"IRCTC booking rules for retiring rooms."
    • addedOutput schema / properties / stations / description
      Added value: +"Stations with IRCTC retiring rooms, nearest first."
    • addedOutput schema / properties / stations / items / properties / distance_km / description
      Added value: +"Straight-line distance from the search place, km; 0 for the station itself."
    • addedOutput schema / properties / stations / items / properties / lat / description
      Added value: +"Station latitude (null if unknown)."
    • addedOutput schema / properties / stations / items / properties / lng / description
      Added value: +"Station longitude (null if unknown)."
    • addedOutput schema / properties / stations / items / properties / managed_by / description
      Added value: +"Who runs the retiring rooms, as IRCTC lists it."
    • addedOutput schema / properties / stations / items / properties / station_code / description
      Added value: +"Station code."
    • addedOutput schema / properties / stations / items / properties / station_name / description
      Added value: +"Station name."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: what the records contain (booking rules, indicative price ranges, portal link) and the important limitation that availability/prices are not live and depend on a Confirmed or RAC PNR.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core purpose, then inputs, then the binding caveat. Very little waste, though the parenthetical definition of retiring rooms is slightly verbose for an agent audience.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be enumerated, yet the description still summarizes them usefully. With annotations covering the read-only profile and the schema covering all params, nothing needed to invoke the tool correctly is missing; the PNR/portal caveat closes the main expectation gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all six parameters (lat/lng, iata, place, radius_km, station_code) are already documented with examples and constraints. The description only restates the station-code and radius-of-a-place modes without adding format or precedence guidance (e.g. what happens if both place and station_code are supplied). Baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (Lists) and a specific resource (Indian Railways stations with IRCTC retiring rooms), and even defines the domain term in parentheses. It is clearly distinct from siblings such as search_hotels and get_hotel_details, which cover commercial lodging.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It spells out the two accepted lookup modes (a station code, or a radius around a place) and sets an explicit boundary: live availability and exact prices are 'not available here' and require a PNR on the IRCTC portal. That is clear when-not guidance, though it does not name a sibling tool as the alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.