Skip to main content
Glama

Arrival board for a station

get_arrivals
Read-only

Retrieve live arrival times for a Swiss public transport station by name, with an optional result limit. Use it to check upcoming arrivals and plan trips.

Instructions

Live arrival board for a Swiss public transport 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
limitNo
stationYesStation name, e.g. 'Bern'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-data profile is covered. The description adds one useful behavioral fact – the board is live/real-time – but says nothing about data freshness, what happens with an ambiguous or unknown station, or service outages, which are the real risks for an open-world query.

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?

A single front-loaded sentence with zero padding or redundancy. Its brevity tips into under-specification, but that is penalized under the other dimensions rather than here.

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

Completeness2/5

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

For a board tool with no output schema, the description should indicate what an arrival entry contains (line, destination, scheduled vs. actual time, delays) and roughly how many results to expect. None of that is present, so the agent must call it blind on the return shape.

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 50%: 'station' is documented with an example in the schema, and 'limit' is self-explanatory through its type, default, minimum and maximum. The description adds no parameter meaning of its own, but the structured fields are sufficient for an agent to supply both values without further explanation.

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

Purpose4/5

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

States a specific resource ('Live arrival board') and scope ('Swiss public transport station'), and 'arrival' implicitly distinguishes it from the sibling get_departures. It stops short of explicitly naming the sibling relationship, but an agent can select correctly from the name and sentence alone.

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: no statement of prerequisites (does the station name need an exact match?), no exclusions, and no pointer to alternatives such as get_departures or get_connections. At best, the word 'Live' hints at real-time use, but that is inference rather than guidance.

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