Skip to main content
Glama

get_departures

Read-onlyIdempotent

Retrieve live departures from a specified Swiss station, with optional departure limit and date/time filters, to check upcoming public transport connections.

Instructions

Live departures from a station

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

Input Schema

NameRequiredDescriptionDefault
limitNodefault: 10
stationYesStation name
datetimeNoYYYY-MM-DDTHH:MM, default: now

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • changedInput schema / properties / datetime / description
      Previous value: -"DateTime YYYY-MM-DDTHH:MM (default: now)"New value: +"YYYY-MM-DDTHH:MM, default: now"
    • changedInput schema / properties / limit / description
      Previous value: -"Number of departures (default: 10)"New value: +"default: 10"
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and side-effect questions are answered structurally. The description adds only the word "live," which usefully implies a real-time feed that changes between calls, but says nothing about freshness, rate limits, or the time window covered by results.

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 four-word fragment with zero padding and the key qualifier ("live") front-loaded. It is efficient, though its brevity shades into under-specification rather than discipline.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an open-world, real-time tool with no output schema, the agent needs to know the return shape, the default time horizon of "departures," and timezone handling, and none of that is present. Combined with the absence of usage guidance, the definition leaves real gaps an agent would hit on first invocation.

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% and every parameter carries a description, including the YYYY-MM-DDTHH:MM format and defaults, so the schema does the heavy lifting. The description adds no meaning beyond it — notably it does not say whether "station" accepts a free-text name or an ID, nor what the limit bounds.

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 "Live departures from a station" states the resource (departures) and the required input (station), and the word "live" signals real-time data rather than schedules. It is clear what the tool returns, but it never distinguishes itself from adjacent siblings such as get_arrivals or get_connections, which an agent must choose between.

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 exclusion of alternatives, and no mention of prerequisites such as first resolving a station via search_stations. The agent is left to infer the departures-vs-arrivals-vs-connections split purely from tool names.

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