Gaduin

Train station board

get_station_board

Read-onlyIdempotent

Live departures and arrivals at a railway station found by name or station code: for each train still to come, the other end of its journey, scheduled, expected and actual times in UTC, platform, status, delay, operator and, when one is open, a link to its market; plus the coming hour's departures, late and cancelled counts, and a link to the station page on gaduin.com. Finds stations that have a page on gaduin.com.

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

Input Schema

Name	Required	Description
`limit`	No	Max trains per direction (1-30). Defaults to 10.
`network`	No	The railway's country code to narrow the match, e.g. GB, US or CH.
`station`	Yes	Station name or code, e.g. London Paddington, PAD or Zürich HB.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds meaningful behavior beyond that: times are in UTC, only trains 'still to come' are returned, market links appear only 'when one is open', and station coverage is limited to those with a gaduin.com page. It does not address pagination or truncation behavior.

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?

It is a single dense sentence, but front-loaded with the core action and payload, and every clause carries information about what is returned. The enumerated field list is long yet earns its place given there is no output schema.

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

Completeness5/5

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

With no output schema, the description carries the full burden of describing returns and does so thoroughly: per-train times, platform, status, delay, operator, market link, plus aggregate counts and a station-page link. Combined with annotations and a fully documented schema, an agent has what it needs to call the tool correctly.

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%, so the baseline is 3. The description reinforces the station parameter's accepted forms (name or code) but says nothing about 'limit' (max trains per direction) or 'network' (country code), leaving those entirely to the schema.

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?

States a specific verb and resource: 'Live departures and arrivals at a railway station found by name or station code', then enumerates the exact payload. It is unmistakably distinct from the aviation and market siblings, so an agent can select it without opening the schema.

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 is implied by the description (station lookup by name or code) and one real constraint is given: 'Finds stations that have a page on gaduin.com.' However, there is no explicit when-to-use versus when-not framing, and no alternatives are named or ruled out.

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

All Gaduin 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.

Resources

Need Help?