Skip to main content
Glama

Platforms and track-free access at an SBB station

get_station_platforms
Read-only

Retrieve an SBB station's platforms with number, type, length and step-free access details, so you can check accessibility and whether long trains fit.

Instructions

The platforms of an SBB station: number, type, length in metres, and whether passengers can reach them without crossing tracks (underpass, overpass or level access). Useful for accessibility and for long trains. Example: {station:'Bern'}.

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

Input Schema

NameRequiredDescriptionDefault
stationYesOfficial station name, e.g. 'Bern'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4/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 and openness are covered. The description adds genuine domain context beyond them: it spells out what 'track-free access' means (underpass, overpass, level access) and clarifies that length is in metres. It stops short of covering failure behavior for unknown station names, which keeps it from a 5.

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?

Two compact sentences, front-loaded with the subject and return fields before the use-case note and example. Every clause contributes information; nothing is redundant padding.

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?

There is no output schema, so describing the returned fields is essential and the description does it well, including the access-type parenthetical. The only gap is what happens when a station name is unmatched or ambiguous, which an agent would want to know for a single-required-param lookup tool.

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 coverage is 100% and the single parameter already documents 'Official station name, e.g. Bern'. The description's example {station:'Bern'} merely repeats the schema example, adding no new meaning such as name-format rules or accepted aliases. Baseline 3 applies when the schema carries the parameter semantics.

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?

States a specific verb and resource (platforms of an SBB station) and enumerates exactly what is returned: number, type, length in metres, and track-free reachability. The scope is narrow enough that an agent can distinguish it from get_arrivals, get_departures, or get_station_ridership without opening 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?

The phrase 'Useful for accessibility and for long trains' implies when to reach for it, but there is no explicit when-not guidance and no named alternative tool for adjacent needs (e.g. live departure data). Usage context is suggested rather than specified.

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