Skip to main content
Glama

Departure board for a station

get_departures
Read-only

Retrieve live departure times, delays, and platform information for a Swiss public transport station by name, with an optional limit on results.

Instructions

Live departure board for a Swiss public transport station, with delays and platforms.

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_departures"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
stationYesStation name, e.g. 'Basel SBB'

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 safety and openness are covered. The description adds that results include delays and platforms, which is genuinely useful return-content context, but says nothing about the time window covered, ordering, or how the limit interacts with live data.

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 no filler; the resource and its distinguishing qualities (live, delays, platforms) come first. It is efficient rather than padded, though it is thin for a tool with real-time semantics.

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?

There is no output schema, so the description carries the burden of explaining what comes back, and it does so only in three words (delays, platforms). Questions an agent must resolve before calling — how far ahead departures go, whether past departures appear, what limit caps — are unaddressed.

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?

At 50% schema coverage, the station parameter is documented in the schema itself while limit is not, and the description does not compensate for that gap (no default, no max, no meaning). It does confirm the tool is station-scoped and implies Swiss-only naming, which is marginal added value over the schema.

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?

The description states a specific verb+resource: a live departure board for a named Swiss public transport station. It is clearly not an arrivals board or a connection planner, though it never explicitly contrasts itself with the nearby get_arrivals sibling.

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 guidance on when to use this rather than get_arrivals, get_connections, or get_station_platforms, all of which an agent could plausibly confuse with it. The only usage signal is implicit: the word 'live' hints at real-time results.

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