Skip to main content
Glama

Get one train

get_train
Read-onlyIdempotent

Use for the full platform status of one train, including departed, due_now and platform_withdrawn trains. Give train_id (from get_departures or find_train), or a headcode plus time (HH:MM today). Several matches return candidates, a headcode alone returns train_needs_time, and a train no longer on the board returns train_not_on_board, which is not retryable. Read only. Predictions are unofficial and may be wrong. Station screens are the official source.

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": "get_train"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNoHH:MM today, with headcode.
stationNoStation code, for example EUS or PAD. Default EUS. Call list_stations to see which are live.
headcodeNoTrain headcode, an alternative to train_id when given with time.
train_idNoTrain id from get_departures or find_train.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / station / description
      Previous value: -"Station code, for example EUS. Default EUS."New value: +"Station code, for example EUS or PAD. Default EUS. Call list_stations to see which are live."
    • addedInput schema / properties / train_id / description
      Added value: +"Train id from get_departures or find_train."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld), it discloses the actual outcome states an agent will encounter: candidates on multiple matches, train_needs_time for a bare headcode, and train_not_on_board flagged as not retryable. It also warns that predictions are unofficial and station screens are authoritative, which is real behavioral context an agent could not infer from the schema.

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

Conciseness5/5

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

The purpose and lookup paths are front-loaded, and every sentence carries distinct information: input forms, three outcome states, retryability, and the accuracy caveat. No filler or repetition of the tool name.

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

Completeness4/5

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

For a read-only lookup with no output schema, the definition covers inputs, failure modes and accuracy caveats well. Minor gaps remain, such as how the station parameter interacts when a train_id is supplied and what a 'candidates' response looks like, but nothing critical to calling it is missing.

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 coverage is 100%, so train_id, headcode, time and station are already documented in the schema, and the description largely restates those sources and formats. It adds only modest value, such as confirming the headcode-plus-time pairing requirement and the identifier provenance; a baseline 3 is appropriate.

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 gives a specific verb and resource ('full platform status of one train') and then narrows scope by naming which train states are covered (departed, due_now, platform_withdrawn). It also ties the input identifiers back to the sibling tools get_departures and find_train, so an agent can see how this differs from searching.

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 clearly explains the two accepted lookup paths (train_id, or headcode plus an HH:MM time) and where those identifiers come from. It stops short of an explicit 'use find_train instead when you only have text/fuzzy input' exclusion, but the identifier-source guidance effectively routes the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources