Skip to main content
Glama

get_arrivals

Read-onlyIdempotent

Retrieves live arrival times for a specified Swiss station, optionally filtered by date/time and result limit. Use it to check when trains or other transport will arrive at a station.

Instructions

Live arrivals at a station

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "station": "<station>"
    },
    "name": "get_arrivals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNodefault: 10
stationYesStation name
datetimeNoYYYY-MM-DDTHH:MM, default: now

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • changedInput schema / properties / datetime / description
      Previous value: -"DateTime YYYY-MM-DDTHH:MM (default: now)"New value: +"YYYY-MM-DDTHH:MM, default: now"
    • changedInput schema / properties / limit / description
      Previous value: -"Number of arrivals (default: 10)"New value: +"default: 10"
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so safety and caching behavior are covered. The single word 'Live' adds real information beyond that: results are real-time rather than scheduled, which is meaningful for a transport tool. It says nothing about latency, caching, or what happens with an unknown station.

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

Conciseness3/5

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

Five words with zero waste and the key qualifier ('Live') front-loaded, which is good. But at this length it is under-specified rather than concise given three parameters and many close siblings.

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

Completeness3/5

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

The tool is simple, the schema is fully self-documenting, and annotations cover the safety profile, so the bar is low. Still, with no output schema and no hint about the shape of an arrival record (line, destination, time, delays) or station identifier format, the agent is guessing at what comes back.

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 'station', 'limit' (default 10) and 'datetime' (YYYY-MM-DDTHH:MM, default now) are fully documented in the schema. The description adds no extra meaning about parameter interaction, such as whether 'datetime' returns future arrivals or filters live ones. Baseline 3 applies.

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

Purpose3/5

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

The fragment 'Live arrivals at a station' names the resource (arrivals) and the required input (station), which is enough to infer the function. But it has no verb and never contrasts itself with the very similar sibling get_departures, so differentiation rests entirely on the tool name.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing about choosing this over get_departures, get_connections, or get_nearby_stations, and no note on whether a station ID or name is preferred. The agent must infer everything from the name.

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

Deploy Server

Other Tools