Skip to main content
Glama

get_departures

Retrieve live departure times from Swiss transport stations to plan journeys and check schedules.

Instructions

Get live departures from a Swiss transport station

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stationYesStation name
limitNoNumber of departures (default: 10)
datetimeNoDateTime YYYY-MM-DDTHH:MM (default: now)

Implementation Reference

  • The handler function that executes the 'get_departures' tool by calling the /stationboard API endpoint with type="departure".
    case "get_departures": {
      const url = buildUrl(`${BASE}/stationboard`, {
        station: args.station as string,
        limit: args.limit as number,
        datetime: args.datetime as string,
        type: "departure",
      });
      const data = await fetchJSON<{ station: Station; stationboard: BoardEntry[] }>(url);
      return JSON.stringify({
        station: data.station?.name,
        departures: data.stationboard.map(slimBoardEntry),
      });
    }
  • The input schema definition for the 'get_departures' tool.
    {
      name: "get_departures",
      description: "Get live departures from a Swiss transport station",
      inputSchema: {
        type: "object",
        required: ["station"],
        properties: {
          station: { type: "string", description: "Station name" },
          limit: { type: "number", description: "Number of departures (default: 10)" },
          datetime: { type: "string", description: "DateTime YYYY-MM-DDTHH:MM (default: now)" },
        },
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get live departures' implies a read-only operation, it doesn't specify whether this requires authentication, has rate limits, what format the data returns, or whether it's real-time versus cached data. The description adds minimal behavioral context beyond the basic operation.

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?

The description is a single, efficient sentence that states exactly what the tool does without unnecessary words. It's appropriately sized for a straightforward data retrieval tool and gets directly to the point with zero wasted verbiage.

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?

For a read-only data retrieval tool with good schema coverage but no output schema, the description provides basic context but lacks important details. Without annotations or output schema, the description should ideally mention what format the departures data returns (e.g., list of departures with times/destinations) or any notable behavioral characteristics. It's minimally adequate but has clear gaps.

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?

With 100% schema description coverage, the input schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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 description clearly states the action ('Get live departures') and the resource ('from a Swiss transport station'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_arrivals' or 'get_connections' which likely serve related but distinct purposes in the transport domain.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'get_arrivals', 'get_connections', and 'get_nearby_stations' available, there's no indication of how this tool differs or when it's the appropriate choice. The description only states what it does, not when to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vikramgorla/mcp-swiss'

If you have feedback or need assistance with the MCP directory API, please join our Discord server