Skip to main content
Glama

Swiss public transport

connections

Read-only

Public transport connections from A to B: times, platforms, delays, changes, lines.

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": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
viaNoUp to two stations the journey must pass.
dateNoYYYY-MM-DD; today if left out.
timeNohh:mm, Swiss local time; now if left out.
limitNoNumber of connections.
originYesStart: station name or id, address or place.
arrive_byNoTrue if `time` is the latest arrival rather than departure.
destinationYesDestination, like origin.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive, open-world access, and an output schema exists, so the description only needs to add context. It signals that live data including delays is returned, which hints at real-time source behavior, but says nothing about coverage area, rate limits, or failure modes when a station cannot be resolved.

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?

A single front-loaded sentence with zero filler; the resource and the returned fields come first and nothing is repeated. It is exactly as long as it needs to be for the information it carries.

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 100% schema coverage, rich annotations, and an output schema, the description covers the essentials for calling the tool correctly. The only real gap is that nothing distinguishes this from the departures sibling or explains the real-time nature of the data source.

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 all seven parameters including via, date, time, limit, and arrive_by are already documented in the schema. The description adds no parameter-level meaning beyond the schema, which is the expected baseline when the schema does the work.

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?

"Public transport connections from A to B" names the resource and the required inputs, and the trailing list (times, platforms, delays, changes, lines) specifies what the result contains. It implicitly separates itself from departures/stations siblings by being journey-based rather than board-based, though it never states that distinction outright.

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 A-to-B framing implies journey planning, so an agent can infer when this applies, but there is no explicit when-to-use or when-not-to-use guidance and no reference to the departures tool that handles the single-station case. Usage is left to inference.

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