Skip to main content
Glama

get_connections

Read-onlyIdempotent

Find train and bus connections between two locations in Switzerland, optionally for a specific date, time, or arrival time, and limit the number of results.

Instructions

Train/bus connections between two locations

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
toYesStation or address
dateNoYYYY-MM-DD, default: today
fromYesStation or address
timeNoHH:MM, default: now
limitNo1-16, default: 4
isArrivalTimeNoTreat time as arrival time

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.9.0
    • changedInput schema / properties / date / description
      Previous value: -"Date YYYY-MM-DD (default: today)"New value: +"YYYY-MM-DD, default: today"
    • changedInput schema / properties / from / description
      Previous value: -"Departure station/address"New value: +"Station or address"
    • changedInput schema / properties / isArrivalTime / description
      Previous value: -"True if time is arrival time"New value: +"Treat time as arrival time"
    • changedInput schema / properties / limit / description
      Previous value: -"Number of connections (1-16, default: 4)"New value: +"1-16, default: 4"
    • changedInput schema / properties / time / description
      Previous value: -"Time HH:MM (default: now)"New value: +"HH:MM, default: now"
    • changedInput schema / properties / to / description
      Previous value: -"Arrival station/address"New value: +"Station or address"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether results are real-time or scheduled, how many connections come back, or whether it is Swiss-only despite the openWorldHint.

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?

A single seven-word fragment with zero waste and the resource front-loaded. It is efficient, though the terseness leaves the agent with almost no context to act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should indicate what a 'connection' returns (legs, departure/arrival times, duration, transfers) and hint at data currency. Parameter documentation is complete via the schema, so the gap is limited to return-value context for a moderately simple 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 description coverage is 100%, with every parameter including formats (YYYY-MM-DD, HH:MM) and defaults (today, now, limit 4) documented in the schema. The description adds no further meaning, such as how isArrivalTime changes which connections count, so the baseline 3 applies.

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 phrase 'Train/bus connections between two locations' names a specific resource (public-transport connections) and scope (origin-to-destination journey), which implicitly distinguishes it from sibling station-board tools like get_departures and get_arrivals. It stops short of explicitly naming those siblings, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives such as get_departures/get_arrivals for a single station, and no prerequisites or exclusions. The only usage signal is the phrase 'between two locations', which the agent must infer selects this tool over the departures board.

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