Skip to main content
Glama

Passengers per day at an SBB station

get_station_ridership
Read-only

Retrieve average daily boardings and alightings for an SBB station by year, including change from the previous year, using the official station name; close matches are suggested.

Instructions

Average daily boardings and alightings at an SBB station (all days, weekdays, weekends), by year, with the change against the previous year. Use the official station name; close matches are suggested if it is not exact. Example: {station:'Zürich HB'}.

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

Input Schema

NameRequiredDescriptionDefault
yearsNoHow many recent years to return
stationYesOfficial station name, e.g. 'Bern', 'Zürich HB', 'Lausanne'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds real behavior beyond that. It discloses the output shape (boardings/alightings split by day type and year, with prior-year delta) and the fuzzy-match fallback when the name is not exact, which an agent could not infer otherwise.

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?

Two sentences plus a short example, with the core capability front-loaded and the naming caveat placed after. The example ('{station:'Zürich HB'}') largely duplicates the schema's own examples, which is the only wasted element.

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 no output schema, the description does the necessary work of summarizing return values and the year-over-year delta. For a simple two-parameter read tool with full schema coverage and annotations, only minor gaps remain (units, behavior when no station matches at all).

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 100%, so baseline is 3; the description still adds value by explaining that a non-exact station name triggers suggested close matches rather than failing outright. The 'years' parameter is only indirectly addressed via 'by year', so it does not fully explain the lookback window.

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 concrete verb+resource pair ('Average daily boardings and alightings at an SBB station') and enumerates the returned breakdowns (all days, weekdays, weekends, by year, plus year-over-year change). This clearly separates it from siblings such as get_station_punctuality or get_station_platforms without needing to open 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 Guidelines3/5

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

It gives a usage rule for the station argument ('Use the official station name; close matches are suggested if it is not exact'), which is genuinely helpful for invocation. However, it offers no guidance on when to choose this tool over related station tools, nor any exclusions or prerequisites, so usage is only implied by the topic.

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