Skip to main content
Glama

Current public-transport disruptions (Switzerland)

get_transport_disruptions
Read-only

Retrieve current and planned Swiss public transport disruptions, including cause, affected lines and stops, and filter results by station, operator, or free text.

Instructions

Current and planned disruptions on Swiss public transport (trains, trams, buses, boats) from opentransportdata.swiss service alerts: title, description, cause/effect, validity periods, affected operators/lines/stops. Filter by free text (text: 'Bauarbeiten'), operator (agency id like '11' for SBB, or name), or station (name or UIC number, e.g. 'Olten' or '8500218'). Requires the server env var OPENTRANSPORTDATA_API_KEY (free key); otherwise returns instructions. Example: {station: 'Luzern', lang: 'de'}.

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

Input Schema

NameRequiredDescriptionDefault
langNoen
textNoSubstring in title/description, e.g. 'Streckenunterbruch'
limitNo
stationNoStation name or 7-digit UIC number
operatorNoGTFS agency id (e.g. '11' = SBB) or operator name
active_onlyNoOnly disruptions whose validity covers now

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior: a required OPENTRANSPORTDATA_API_KEY and the fallback of returning instructions when it is missing. It says nothing about rate limits, pagination over the limit parameter, or how partial failures are reported, so the added value is real but narrow.

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?

The description is front-loaded with scope, then filtering, then the prerequisite, then an example – a logical order with no filler. It is dense with parentheticals and slightly compressed, but every sentence carries information.

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

Completeness4/5

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

With six optional parameters, no output schema, and annotations covering only safety, the description compensates by listing the returned fields (title, description, cause/effect, validity periods, affected operators/lines/stops) and the auth prerequisite. Pagination behavior for limit is the main remaining gap.

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 67%, and the description supplies meaning for the loosely specified filters – operator as GTFS agency id with a concrete value, station as name or 7-digit UIC, and a language choice in the example. limit and active_only are left to the schema, where active_only is documented and limit is self-explanatory from its bounds and default.

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 description names a specific verb and resource ('Current and planned disruptions on Swiss public transport') plus the data source (opentransportdata.swiss service alerts) and enumerates what each record contains. An agent can immediately distinguish this from sibling schedule tools such as get_connections or get_departures.

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 context for use and concrete filtering recipes ('Bauarbeiten', agency id '11' for SBB, station 'Olten'/'8500218') plus a worked example call. It stops short of explicitly naming alternatives or stating when not to use it, so it does not reach the top band.

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