Skip to main content
Glama

Swiss public transport

departures

Read-only

The departure (or arrival) board of a station, with platforms and delays.

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

Input Schema

NameRequiredDescriptionDefault
whenNo'YYYY-MM-DD hh:mm', Swiss local time; now if left out.
limitNoNumber of entries.
stationYesStation name or id.
arrivalsNoTrue for arrivals instead of departures.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile and live-data nature are covered. The description adds only that results include platforms and delays, which is largely redundant with the output schema; it says nothing about freshness, coverage, or how empty results are handled.

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. It is efficient, though slightly thin — one clause about the response payload covers both the resource and output in a way that is dense but clear.

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

Completeness3/5

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

With an output schema, rich annotations, and full parameter documentation, most of the burden is carried elsewhere; the description need not explain return values. What remains missing is routing guidance between this tool and connections, which the definition does not supply.

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%, so station, when, limit, and arrivals are all fully documented in the schema. The description only echoes the arrivals behavior already spelled out in the arrivals parameter, adding no format or defaulting detail.

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?

Names a concrete resource — the departure board of a station — and states what it returns (platforms and delays). The parenthetical 'or arrival' clarifies scope, though it does not explicitly distinguish the tool from siblings like connections, which an agent must infer from the response shape.

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, no prerequisites, and no mention of an alternative tool. An agent must infer from the sibling list whether to use this or connections for a journey query.

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