Skip to main content
Glama

get_arrivals

Retrieve live arrival times at Swiss transport stations to check upcoming departures and plan journeys using real-time public transit data.

Instructions

Get live arrivals at a Swiss transport station

Input Schema

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

Implementation Reference

  • Handler logic for the "get_arrivals" tool in transport.ts.
    case "get_arrivals": {
      const url = buildUrl(`${BASE}/stationboard`, {
        station: args.station as string,
        limit: args.limit as number,
        datetime: args.datetime as string,
        type: "arrival",
      });
      const data = await fetchJSON<{ station: Station; stationboard: BoardEntry[] }>(url);
      return JSON.stringify({
        station: data.station?.name,
        arrivals: data.stationboard.map(slimBoardEntry),
      });
    }
  • Schema definition for the "get_arrivals" tool.
      name: "get_arrivals",
      description: "Get live arrivals at a Swiss transport station",
      inputSchema: {
        type: "object",
        required: ["station"],
        properties: {
          station: { type: "string", description: "Station name" },
          limit: { type: "number", description: "Number of arrivals (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 the full burden of behavioral disclosure. It mentions 'live arrivals' which implies real-time data, but doesn't disclose rate limits, data freshness, error conditions, authentication needs, or what the response format looks like. This leaves significant gaps for an agent to understand operational behavior.

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 with zero wasted words. It's appropriately sized for a simple query tool and front-loads the essential information about what the tool does.

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?

Given the tool's moderate complexity (3 parameters, no output schema, no annotations), the description is minimally adequate. It states the core purpose but lacks behavioral context, usage guidance, and output information. The schema handles parameter documentation well, but the overall picture remains incomplete for an agent to use the tool confidently.

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?

The input schema has 100% description coverage, providing clear documentation for all three parameters. The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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 tool's purpose: 'Get live arrivals at a Swiss transport station.' It specifies the verb ('Get'), resource ('arrivals'), and geographic scope ('Swiss transport station'). However, it doesn't explicitly differentiate from its sibling 'get_departures' or other transport-related tools, which prevents a perfect score.

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. It doesn't mention sibling tools like 'get_departures' or 'get_connections' for related transport queries, nor does it specify prerequisites or contextual constraints for usage.

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