Skip to main content
Glama

disruptions

Read-only

Aktuelle Störungen, Baustellen und Liniensperrungen im ÖPNV. Für „gibt es Störungen", „Ausfälle in X" ist dieses Werkzeug die Auskunft. Datenlage — wichtig: Ob eine leere Antwort von disruptions eine Entwarnung ist, sagt jede Antwort selbst (coverage, coverage_regions). Nur bei covered_no_disruptions heißt eine leere Liste „keine Störungen"; bei covered_no_placed_disruptions, feed_stale_for_area, no_feed_for_area, area_unknown und feed_unavailable ist sie keine Entwarnung, covered_with_disruptions trägt verortete Meldungen. (Verbindungen und Abfahrten sind davon nicht betroffen — die gelten für Deutschland, Österreich, die Schweiz, Südtirol und die anderen Länder ringsum, deren Fahrplan vorliegt.) Keine Pflicht-Args — ohne Filter kommen die aktiven Meldungen, gekappt auf limit. Optional: line (Liniennummer/-token, z.B. '6', 'U3') und stop (Haltestellen-Name) verknüpfen UND; area (Stadt/Gemeinde) bestimmt das coverage und sortiert die unverorteten Meldungen — es unterdrückt sie nicht: die kommen getrennt in unplaced zurück, auch ohne area. Nenne nur Filter, die der Nutzer wirklich nannte. Format: kompakter Einrück-Text (TOON), kein JSON; die Schreibweise steht in der Anleitung. Anleitung: get_usage_guide mit tool='disruptions' — coverage_regions, die beiden Listen, die Felder einer Meldung und woran eine gekappte Antwort zu erkennen ist. Anti-Fab: nur zurückgegebene Meldungen nennen; eine Meldung ohne betroffene Linie und ohne betroffenen Halt ist eine allgemeine Störung und wird keiner Linie zugeschrieben, eine Meldung aus unplaced keinem Ort.

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

Input Schema

NameRequiredDescriptionDefault
areaNoArea or city name (`"Hannover"`). Matches the municipality the affected stops lie in, and decides the `coverage` the answer reports. It never suppresses a report: the ones it cannot place come back in `unplaced`.
lineNoLine token as printed on the vehicle (`"6"`, `"169"`, `"U3"`). A disruption is kept only if it names that line — under one of its `affected_lines` or one of its `affected_line_refs`.
stopNoStop name (`"Kröpcke"`). Case-insensitive substring match against the disruption's `affected_stops`.
limitNoMaximum number of disruptions, at least 1. Default 5, values above 15 are served as 15. It shortens the answer, it does not choose better entries — an answer that had to leave something out says so (`truncated` + `total`).
formatNoAnswer serialisation: `"toon"` (default) or `"json"` — the detail is in `get_usage_guide`. **An agent leaves this out.**
include_unplacedNo`false` leaves the `unplaced` list out of the answer (default `true`). It only shortens the answer — `coverage` still counts what was left out, so it never turns into an all-clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Disruption query. All three filters are optional; with\nnone set, ALL active disruptions are returned (\"alle aktiven\"). At least one\nfilter narrows the result — never guess a line/stop the user did not name."New value: +"Disruption query. All three filters are optional; with\nnone set, the active disruptions are returned (\"alle aktiven\"), capped at\n`limit` (`truncated`/`total` say where the cap cut). At least one filter\nnarrows the result — never guess a line/stop the user did not name."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description carries real behavioural payload: it enumerates the coverage statuses and explains that only `covered_no_disruptions` makes an empty list an all-clear, while stale, missing-feed and unknown-area states do not. It also discloses truncation signalling (`truncated`/`total`), the unplaced list behaviour, output serialisation (TOON, not JSON), and anti-fabrication rules about not attributing line-less/unplaced reports.

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?

Purpose and the critical 'empty is not always an all-clear' caveat are front-loaded, and most sentences carry unique information. It is dense and slightly repetitive (get_usage_guide is referenced twice, and some coverage enumeration duplicates schema text), which keeps it from a 5.

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?

No output schema exists, yet the description explains the answer shape (coverage, the two lists, unplaced), how truncation is detected, and the TOON format, plus a pointer to get_usage_guide for field-level detail. For a 6-parameter, zero-required read tool with annotations, nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3; the description still adds meaning by stating that `line` and `stop` combine with AND and that `area` determines coverage and separates rather than suppresses unplaced reports. It reinforces the limit cap and the include_unplaced caveat, which the schema also documents, so the gain is modest but genuine.

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 sentence names a concrete resource class (aktuelle Störungen, Baustellen, Liniensperrungen im ÖPNV) and explicitly frames the tool as the answer to "gibt es Störungen" / "Ausfälle in X". It also delimits scope against neighbouring capabilities by noting that connections and departures are not affected, so an agent can tell it apart from show_connections/show_departures without opening a schema.

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 gives clear when-to-use phrasing (disruption questions, outages in an area) and states that no arguments are required, with filters only when the user actually named them. It does not explicitly name a sibling as the alternative for an adjacent need (e.g. point to departures for schedule questions), so the routing guidance is contextual rather than exhaustive.

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