Skip to main content
Glama

Yesterday's punctuality at an SBB station

get_station_punctuality
Read-only

Retrieve previous operating day's punctuality at a Swiss station from SBB actual times: stops, on-time arrival/departure shares, cancellations and delayed lines; optionally filter by line.

Instructions

Punctuality at a station on the previous operating day, from SBB's published actual times: number of stops, share of on-time arrivals and departures (SBB's delay threshold, about 3 minutes), cancellations, and the lines with the most delayed arrivals. Optional line filter (e.g. 'IC1', 'S3'). Example: {station:'Olten'}.

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

Input Schema

NameRequiredDescriptionDefault
lineNoOnly this line, e.g. IC1, IR15, S3
stationYesOfficial stop name, e.g. 'Olten', 'Zürich HB'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds meaningful context: the data comes from SBB's published actual times, covers the previous operating day, uses SBB's roughly 3-minute delay threshold, and lists what the response includes. It does not discuss data freshness or availability limits, but it goes well beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with the purpose and time scope, then enumerates the returned data and closes with the optional filter and a compact example. Every element earns its place and there is no filler.

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?

For a two-parameter, read-only tool with no output schema, the description supplies the source, time window, metrics, and an example. It is close to complete, though it could mention whether data can be missing or how cancelled trips are represented.

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?

The input schema already documents both parameters at 100% coverage. The description reinforces the optional line filter and provides an example, but adds little semantic meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 resource (punctuality at a station), a precise time window (previous operating day), and the exact metrics returned. It is clear what the tool does, but it does not explicitly distinguish it from sibling tools such as get_arrivals 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 Guidelines3/5

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

Usage is implied by the previous-operating-day scope and the optional line filter, but there is no explicit guidance on when to use this tool versus alternatives. No exclusions or sibling comparisons are provided.

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