Skip to main content
Glama

Next bus and train departures

next_departures
Read-onlyIdempotent

Next scheduled direct bus and train departures between Donostia-San Sebastián and a destination: flughafen (Bilbao Airport), hendaye (El Topo train to France), getaria, zarautz, zumaia, orio, deba, hondarribia, pasaia, astigarraga, hernani, tolosa, bilbao, vitoria. Source: open timetable data of the Basque Government (Moveuskadi). Scheduled times, not real-time; times are local (Europe/Madrid).

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": {
      "destination": "<destination>"
    },
    "name": "next_departures"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoOptional local date and time, e.g. "2026-12-19T08:00"; default is now.
limitNoNumber of departures (default 5, maximum 15).
directionNofrom_donostia (default): San Sebastián to the destination; to_donostia: back to San Sebastián.
destinationYesDestination key or name, e.g. "flughafen", "Bilbao Airport", "hendaye", "getaria".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the data source (Moveuskadi), that results are scheduled rather than real-time, that times are local Europe/Madrid, and that only direct connections are returned — a substantive result-shaping constraint.

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?

The key scoping information — origin, destination list, and data caveats — is front-loaded, with the source and time-zone disclaimers trailing efficiently. The dense destination enumeration is long but functional; no sentence is filler, though the paragraph could be broken for readability.

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?

For a simple read-only lookup with full schema coverage and annotations, the description covers what is being queried, the destination vocabulary, and the scheduled-vs-real-time caveat. The main remaining gap is that with no output schema, it does not indicate what a result contains (line numbers, operators, departure times), leaving the agent to discover the return shape.

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 coverage is 100%, so all four parameters are already documented, which sets the baseline at 3. The description does add the fuller destination key list beyond the schema's 'e.g.' examples and reinforces the direct-connection filter, but it says nothing extra about at, limit, or direction semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource — 'Next scheduled direct bus and train departures' — plus an explicit origin/destination scope (Donostia-San Sebastián to a named destination). The enumerated destination keys make it unambiguous which queries this tool answers, distinguishing it from generic siblings like fetch or search.

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 context is implied rather than stated: it is clear this is for upcoming departures between San Sebastián and listed destinations, and the 'scheduled times, not real-time' caveat helps an agent decide relevance. However, it never says when to prefer this over siblings such as trip_check or fetch, nor any exclusions beyond the fixed destination list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources