Portugal (public data)

transit_departures

Scheduled departures from a station or stop (official timetable, not live).

Args: stop: station or stop name, e.g. "Lisboa Oriente", "Cais do Sodré", "Baixa-Chiado", "Prazeres". operator: an operator id (see transit_operators) or a city/region: "porto", "coimbra", "braga", "aveiro", "cascais", "barreiro", "algarve", "faro", "madeira", or "intercity" (FlixBus coaches and CP). Default: CP and the Lisbon operators. when: ISO date-time in Lisbon time, e.g. "2026-11-03T08:00". Default: now. window_minutes: how far ahead to look (max 720). line: keep only a line or destination, e.g. "28E", "Sintra", "Azul".

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": {
      "stop": "<stop>"
    },
    "name": "transit_departures"
  }
}

Input Schema

Name	Required	Description	Default
`line`	No
`stop`	Yes
`when`	No
`limit`	No
`operator`	No
`window_minutes`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and largely meets it: it discloses the static data source, the timezone convention ('Lisbon time'), the maximum look-ahead (max 720), and the default operator set. It does not describe result ordering, behavior when a stop name is ambiguous or unknown, or any rate limits.

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 purpose sentence is front-loaded and the Args block is scannable, with one line per parameter. The long operator enumeration is functional rather than filler, though it is the bulkiest part of an otherwise tight definition.

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?

An output schema exists, so return-value shape need not be explained, and the description covers format conventions, defaults, and limits well for a six-parameter query tool. The remaining hole is the undocumented 'limit' parameter and the lack of guidance on result ordering or empty/ambiguous-result behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does for five of six parameters: it gives concrete stop examples, enumerates accepted operator values plus their default, specifies the ISO format and timezone for 'when', and states the window cap. The sixth parameter, 'limit', is never mentioned, leaving its meaning and interaction with window_minutes undocumented.

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 opening sentence names a specific verb and resource ('Scheduled departures from a station or stop') and immediately qualifies the data source as the official timetable, not live. That qualifier is what separates it conceptually from live-arrival style siblings, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

The '(official timetable, not live)' parenthetical gives a clear condition for choosing this tool over a real-time one, and the defaults ('Default: CP and the Lisbon operators', 'Default: now') tell the agent what happens when optional inputs are omitted. It stops short of explicitly naming a live-data alternative to route to instead.

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

All Portugal (public data) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.