Skip to main content
Glama

Find public transport connections

get_connections
Read-only

Find next Swiss train, bus, tram or boat connections between stations or addresses, with platforms, delays, transfers and per-leg details.

Instructions

Find the next train/bus/tram/boat connections between two Swiss stations or addresses, with platforms, delays, transfers and per-leg details.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "get_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination station or address, e.g. 'Lugano'
viaNoOptional via station
dateNoDate YYYY-MM-DD (default: today)
fromYesOrigin station or address, e.g. 'Zürich HB'
timeNoTime HH:MM (default: now)
limitNo
is_arrival_timeNoIf true, date/time is the desired arrival time

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.6/5.0
Behavior3/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 external-data nature are covered. The description adds useful behavior beyond that — live delay information, platforms, transfers and per-leg breakdown — but says nothing about coverage limits, behavior for unknown stations, or whether results are real-time versus timetable.

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 the action, scope and result contents packed in and no filler. Nothing needs trimming and the key distinction (point-to-point journey) leads.

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 seven parameters, no output schema, and 86% coverage, the description carries the burden of explaining return values, which it does by naming platforms, delays, transfers and per-leg details. Minor gaps remain around empty-result behavior and geographic coverage boundaries.

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 86%, so parameters are largely self-documenting, and the baseline of 3 applies. The description reinforces the from/to semantics ('Swiss stations or addresses') but adds no meaning for via, is_arrival_time, or limit beyond what the schema already states.

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?

States a specific verb (find) and resource (connections) plus transport modes and geography (Swiss stations or addresses), and enumerates the result contents. It is clearly distinguishable from single-station siblings like get_departures/get_arrivals, though no sibling is named explicitly.

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 only implied: an agent infers this is the journey-planning tool between two points. There is no explicit when-to-use guidance, no mention of when to prefer get_departures or get_transport_disruptions, and no stated prerequisites or failure conditions.

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