Skip to main content
Glama

departures

Read-only

Abfahrten oder Ankünfte für EINE Haltestelle — als Daten, für Ergebnisse, die du weiterverarbeitest. Steht show_departures in deinem Werkzeug-Satz, ist das der Vordereingang für die Frage eines Menschen. Für „wann fährt von X", „letzte Stadtbahn von X" kommt die Auskunft aus diesen Werkzeugen; für eine A→B-Frage aus connections. Pflicht ist eine konkrete Stop-id aus einer vorhergehenden Ortsauflösung (z.B. 'de:03241:57'); ein Haltestellen-NAME in id ist ein Argument-Fehler, keine leere Tafel. Optional: time (ohne Versatz MEZ/MESZ) und is_arrival_time; modes (Flüge ['air'], ohne sie ['transit']); direction (Halt-Name, in dessen Richtung gefahren wird) bzw. für eine weiche Angabe target_bearing mit bearing_tolerance; lines (Linie oder Linie@Richtung, wie die Tafel sie an mot.line.direction.ids nennt); arrival_departure; ein Fenster time_range_seconds mit last_of_window; und für den Umfang verbosity, limit sowie render_payload. Für „letzte Bahn heute", „erste S-Bahn morgen" statt der Tafel first_last: je Linie und Richtung erste und letzte Fahrt des Tages (time wählt den Tag). Für „hat X einen Aufzug zur U-Bahn?" statt der Tafel facilities: Aufzüge, Rolltreppen, Rampen des Halts. modes, lines und direction schränken hart ein. Eine leere Tafel ist keine Auskunft: blieb sie mit ['tram'] („Straßenbahn") leer, mit ['tram','subway'] nachfassen — sonst ohne den Filter. Bestellung: eine Abfahrt nur auf Bestellung trägt booking (wer, bis wann, wie) — Frist und Weg mit ihr nennen; „Ruftaxi" nur bei Pflicht. Barrierefreiheit: ob der Halt stufenfrei ist, sagt accessibility. Namen in lang (Vorgabe 'de'), der Name vor Ort daneben in localName — „Meran (Merano)". Anleitung: get_usage_guide mit tool='departures' — erste und letzte Fahrt, Aufzüge, die Echtzeit-, Ausfall- und Zitier-Felder. Anti-Fab: Linien, Richtungen, Zeiten, Gleise, Verspätung, Ausfall und Aufzüge ausschließlich aus dem Output dieses Aufrufs.

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": {
      "id": "<id>"
    },
    "name": "departures"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStop id to read the board of, as the resolver hands it out: a DHID (`"de:03241:57"`, `at:…`, `ch:…`, `it:…`) or a station id (`"Parentch:1:sloid:3000"`). Resolve the stop first — a name here is an argument error.
langNoDie Sprache der Namen: `'de'` (Vorgabe), `'it'`, `'fr'`, auch mit Region (`'de-CH'`).
timeNoISO 8601; without an offset local time in Berlin (`"2026-11-06T08:30"`). Omit for now. Resolve a spoken time with the time tool rather than computing one.
limitNoMaximum number of departures, at least 1. Default 5, values above 15 are served as 15.
linesNoOnly the departures of these lines, by the ids a board writes: the line alone (either direction) as at `mot.line.id`, or line@direction as at `mot.line.direction.ids` (`"de:VBN-VH:6002:_3@0"`); several combine. A line NUMBER (`"9"`) is no id — read the id off a board first. An entry that is no line is an argument error.
modesNoTransport-mode filter; the board then shows nothing else. Entries: `"bus"`, `"tram"`, `"subway"`, `"train"`/`"rail"`, `"ferry"`, `"air"` (flights), `"transit"` (all of them but flights); several combine. Another entry — a street mode, a misspelling — is an argument error, not a dropped filter: a board lists scheduled services. Omitted or empty = all modes. A Stadtbahn or light-rail mention needs BOTH labels — `["tram","subway"]`: which of the two such a network carries depends on the dataset rather than on the vehicle. Set the filter only when the user really asks for a vehicle type; the guide has the rest of the vocabulary and the traps.
formatNoAnswer serialisation: `"toon"` (default) or `"json"` — the detail is in `get_usage_guide`. **An agent leaves this out.**
extendedNo`true` keeps the map data in the text: every stop's coordinate, the whole course of each run, and each departure's way (`pathOnMap`, `pathSource`, `additionalInfos.pathKind`) — for an application that DRAWS the board. It multiplies the answer. A chat client leaves it off.
directionNoName of a stop the user wants to head TOWARD („Richtung Wettbergen") — not a routing destination. The board keeps only departures heading that way, whether the named stop is the terminus or a stop downstream of the queried one. Matching is case-insensitive and area-prefix-tolerant.
verbosityNoHow much of each departure comes back: `"compact"` (default — everything an answer is cited from) or `"full"` (adds the onward stops of the run, and with them the per-stop cancellation marker). A third word is an argument error, not the default.
facilitiesNoInstead of the board, the stop's lifts, escalators and ramps („hat Kröpcke einen Aufzug zur U-Bahn?"): `"elevator"`, `"escalator"`, `"ramp"` or `"all"`; the guide has the fields.
first_lastNo`true` answers instead of the board, per line and direction, the first and the last ride of a day („letzte Bahn heute"): the day running now, or the calendar day of `time` in local time.
last_of_windowNoWhich end of a `time_range_seconds` window to read: omitted or `false` the FIRST departures, `true` the LAST ones (the end-of-service question). An answer carrying `window_truncated: true` beside its board did NOT reach the window's end — its last entry is then not the last departure. Without a window it has no effect.
render_payloadNo`true` appends the same board again as raw JSON, addressed to the user rather than to the model — for an application that draws a departure board. A chat client leaves this off: it is the whole answer twice.
target_bearingNoTarget bearing in degrees, 0 to 360 (0=N, 90=E, 180=S, 270=W), for a SOFT direction („Richtung Norden", „Richtung Stadt") instead of a stop name. The board keeps only departures whose course lies within `bearing_tolerance` of it. Mutually exclusive with `direction`.
is_arrival_timeNo`true` reads `time` as an ARRIVAL time — the same as `arrival_departure = "arrivals"`.
arrival_departureNo`"arrivals"` (when vehicles reach `id`) or `"departures"` (default) — a third value is an argument error. Wins over `is_arrival_time` when both are set.
bearing_toleranceNoAngular tolerance in degrees for `target_bearing`, 0 to 180, only beside it. Default ±60°.
time_range_secondsNoTime WINDOW in seconds, at least 1, starting at `time`. Together with `last_of_window` it reads the last rides before the window ends: pick it so the window ENDS where the question does. The last ride of a day is `first_last`. Omit for a normal next-N lookup.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / bearing_tolerance / description
      Previous value: -"Angular tolerance in degrees for `target_bearing`. Default ±60°."New value: +"Angular tolerance in degrees for `target_bearing`, 0 to 180, only beside it.\nDefault ±60°."
    • changedInput schema / properties / target_bearing / description
      Previous value: -"Target bearing in degrees (0=N, 90=E, 180=S, 270=W) for a SOFT direction\n(„Richtung Norden\", „Richtung Stadt\") instead of a stop name. The board\nkeeps only departures whose course lies within `bearing_tolerance` of it.\nMutually exclusive with `direction`."New value: +"Target bearing in degrees, 0 to 360 (0=N, 90=E, 180=S, 270=W), for a SOFT\ndirection („Richtung Norden\", „Richtung Stadt\") instead of a stop name. The\nboard keeps only departures whose course lies within `bearing_tolerance` of\nit. Mutually exclusive with `direction`."
    • changedInput schema / properties / time_range_seconds / description
      Previous value: -"Time WINDOW in seconds, starting at `time`. Together with `last_of_window`\nit reads the last rides before the window ends: pick it so the window ENDS\nwhere the question does. The last ride of a day is `first_last`. Omit for a\nnormal next-N lookup."New value: +"Time WINDOW in seconds, at least 1, starting at `time`. Together with `last_of_window`\nit reads the last rides before the window ends: pick it so the window ENDS\nwhere the question does. The last ride of a day is `first_last`. Omit for a\nnormal next-N lookup."
  2. Changed3 schema fields changed
    • addedInput schema / properties / time / default
      Added value: +null
    • changedInput schema / properties / time / description
      Previous value: -"ISO 8601 timestamp (e.g. `\"2026-06-15T08:30:00Z\"`). Omit for now. Resolve\na spoken time with the time tool rather than computing one."New value: +"ISO 8601; without an offset local time in Berlin (`\"2026-11-06T08:30\"`). Omit for now.\nResolve a spoken time with the time tool rather than computing one."
    • removedInput schema / properties / time / format
      Removed value: -"date-time"
  3. Changed1 schema field changed
    • changedInput schema / properties / modes / description
      Previous value: -"Transport-mode filter; the board then shows nothing else. Entries:\n`\"bus\"`, `\"tram\"`, `\"subway\"`, `\"train\"`/`\"rail\"`, `\"ferry\"`,\n`\"transit\"`; several combine. Another entry — a street mode, a misspelling\n— is an argument error, not a dropped filter: a board lists scheduled\nservices. Omitted or empty = all modes. A Stadtbahn or\nlight-rail mention needs BOTH labels — `[\"tram\",\"subway\"]`: which of the\ntwo such a network carries depends on the dataset rather than on the\nvehicle. Set the filter only when the user really asks for a vehicle type;\nthe guide has the rest of the vocabulary and the traps."New value: +"Transport-mode filter; the board then shows nothing else. Entries:\n`\"bus\"`, `\"tram\"`, `\"subway\"`, `\"train\"`/`\"rail\"`, `\"ferry\"`, `\"air\"`\n(flights), `\"transit\"` (all of them but flights); several combine. Another entry — a street mode, a misspelling\n— is an argument error, not a dropped filter: a board lists scheduled\nservices. Omitted or empty = all modes. A Stadtbahn or\nlight-rail mention needs BOTH labels — `[\"tram\",\"subway\"]`: which of the\ntwo such a network carries depends on the dataset rather than on the\nvehicle. Set the filter only when the user really asks for a vehicle type;\nthe guide has the rest of the vocabulary and the traps."
  4. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "Die Sprache der Namen: `'de'` (Vorgabe), `'it'`, `'fr'`, auch mit Region (`'de-CH'`).",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Stop id to read the board of, as the resolver hands it out: a DHID (`\"de:03241:57\"`,\n`at:…`, `ch:…`) or a station id (`\"Parentch:1:sloid:3000\"`). Resolve the stop first — a\nname here is an argument error."New value: +"Stop id to read the board of, as the resolver hands it out: a DHID (`\"de:03241:57\"`,\n`at:…`, `ch:…`, `it:…`) or a station id (`\"Parentch:1:sloid:3000\"`). Resolve the stop first — a\nname here is an argument error."
  6. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Stop id to read the board of, as a DHID (`\"de:03241:57\"`; in Austria and\nSwitzerland `at:…`/`ch:…`). Resolve the stop first — a name here is an\nargument error."New value: +"Stop id to read the board of, as the resolver hands it out: a DHID (`\"de:03241:57\"`,\n`at:…`, `ch:…`) or a station id (`\"Parentch:1:sloid:3000\"`). Resolve the stop first — a\nname here is an argument error."
  7. Changed4 schema fields changed
    • changedInput schema / properties / extended / description
      Previous value: -"`true` keeps the map data in the text: every stop's coordinate, the whole\ncourse of each run, and a polyline where the board carries one — for an\napplication that DRAWS the board. It multiplies the answer. A chat client\nleaves it off."New value: +"`true` keeps the map data in the text: every stop's coordinate, the whole\ncourse of each run, and each departure's way (`pathOnMap`, `pathSource`,\n`additionalInfos.pathKind`) — for an application that DRAWS the board. It\nmultiplies the answer. A chat client leaves it off."
    • addedInput schema / properties / facilities
      Added value: +{
      +  "description": "Instead of the board, the stop's lifts, escalators and ramps („hat Kröpcke einen Aufzug\nzur U-Bahn?\"): `\"elevator\"`, `\"escalator\"`, `\"ramp\"` or `\"all\"`; the guide has the fields.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / first_last
      Added value: +{
      +  "description": "`true` answers instead of the board, per line and direction, the first and the last\nride of a day („letzte Bahn heute\"): the day running now, or the calendar day of `time`\nin local time.",
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / time_range_seconds / description
      Previous value: -"Time WINDOW in seconds, starting at `time`. Together with `last_of_window`\nthis answers „letzte Fahrt\": pick it so the window ENDS after end of\nservice (from the evening on, `28800` = 8 h rather than 4 h). Omit for a\nnormal next-N lookup."New value: +"Time WINDOW in seconds, starting at `time`. Together with `last_of_window`\nit reads the last rides before the window ends: pick it so the window ENDS\nwhere the question does. The last ride of a day is `first_last`. Omit for a\nnormal next-N lookup."
  8. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Stop id to read the board of, as a DHID (`\"de:03241:57\"`). Resolve the\nstop first — a name here is an argument error."New value: +"Stop id to read the board of, as a DHID (`\"de:03241:57\"`; in Austria and\nSwitzerland `at:…`/`ch:…`). Resolve the stop first — a name here is an\nargument error."
    • changedInput schema / properties / lines / description
      Previous value: -"Only the departures of these lines, by the ids a board writes: the line alone\n(either direction) as at `mot.line.id`, or line@direction as at\n`mot.line.direction.ids` (`\"de:nds-gvh:gvh-2-9:_1@0\"`); several combine. A line\nNUMBER (`\"9\"`) is no id — read the id off a board first. An entry that is no line\nis an argument error."New value: +"Only the departures of these lines, by the ids a board writes: the line alone\n(either direction) as at `mot.line.id`, or line@direction as at\n`mot.line.direction.ids` (`\"de:VBN-VH:6002:_3@0\"`); several combine. A line\nNUMBER (`\"9\"`) is no id — read the id off a board first. An entry that is no line\nis an argument error."
  9. Changed1 schema field changed
    • addedInput schema / properties / lines
      Added value: +{
      +  "description": "Only the departures of these lines, by the ids a board writes: the line alone\n(either direction) as at `mot.line.id`, or line@direction as at\n`mot.line.direction.ids` (`\"de:nds-gvh:gvh-2-9:_1@0\"`); several combine. A line\nNUMBER (`\"9\"`) is no id — read the id off a board first. An entry that is no line\nis an argument error.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
  10. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, and the description adds real operational heuristics beyond that: an empty board is not an answer (retry with a broader mode set), `booking` obligations for on-demand rides, the `window_truncated` caveat, and strict anti-fabrication rules for lines, times, platforms and delays. It does not describe pagination or the shape of a normal response, but the behavioral guidance is well above what the annotations supply.

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?

The purpose and the stop-id requirement are front-loaded, but the prose is long, densely packed and partly duplicates the already-complete schema (lines, modes, verbosity, first_last, facilities). Much of it earns its place as routing and failure-mode guidance, yet the description could be trimmed without losing agent-usable information.

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?

For a 19-parameter, open-world timetable tool with no output schema, the definition covers the mandatory stop id, the alternatives for first/last and facilities questions, empty-board handling, booking disclosure, accessibility pointers and the guide reference. Nothing essential to calling it correctly is obviously 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 description coverage is 100% and the schema itself already explains `direction` (a stop name to head toward, not a routing destination), `lines` id formats, `modes` vocabulary and `last_of_window` interaction. The description restates these plus a useful "modes, lines and direction restrict hard" note, but adds little meaning the schema lacks, so the baseline 3 applies.

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 opening line names a specific verb and resource ("Abfahrten oder Ankünfte für EINE Haltestelle") and immediately distinguishes this data-oriented tool from the human-facing `show_departures` and the A→B `connections`. An agent can pick this tool over its siblings without opening the schema.

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

Usage Guidelines5/5

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

It routes explicitly: use this board for "wann fährt von X" and "letzte Stadtbahn von X", use `first_last` for first/last-of-day questions, `facilities` for elevator questions, `accessibility` for step-free status, and `connections` for A→B. It also states the mandatory pre-step (resolve the stop id first) and what counts as an argument error.

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