Skip to main content
Glama

Irail Liveboard

irail_liveboard
Read-onlyIdempotent

Live departures board at a Belgian train station, Belgian train times SNCB NMBS. Brussels Antwerp Ghent departures with train number, destination, scheduled time, delay in minutes, platform, and canceled flag. Set type to "arrival" for the arrivals board. Station names accept English exonyms and fuzzy input ("Brussels-South", "Antwerp-Central", "Liège-Guillemins"). Example: irail_liveboard({ station: "Brussels-South" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "station": "Brussels-South"
    },
    "name": "irail_liveboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoBoard type: "departure" (default) or "arrival"
limitNoMax entries to return, 1-50 (default 15)
stationYesBelgian station name, e.g. "Brussels-South", "Antwerp-Central", "Ghent-Sint-Pieters", "Leuven", "Bruges"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "station": "Brussels-South"
      +  },
      +  {
      +    "limit": 20,
      +    "station": "Antwerp-Central",
      +    "type": "arrival"
      +  }
      +]
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered. The description adds useful behavioral context by enumerating the fields returned, which matters because no output schema exists. It does not describe pagination, behavior for unknown or non-Belgian stations, or what a fuzzy-match miss looks like.

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?

Front-loaded with the core purpose, then return fields, then the arrival switch, then station-name tolerance, then a concrete call example. No sentence is wasted, though the city list and the station-example list are mildly redundant keyword reinforcement.

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?

With no output schema, the description correctly carries the burden by listing every returned field, and it explains all three parameters' intent. Missing only edge-case behavior: invalid stations, empty boards, and how limit interacts with results.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by stating that station names tolerate English exonyms and fuzzy input such as 'Brussels-South' and 'Liège-Guillemins', which the schema does not assert. It also restates the arrival mode in prose, reinforcing the enum.

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 board) plus the data it returns: train number, destination, scheduled time, delay, platform, canceled flag. It also explicitly disambiguates the arrivals mode with 'Set type to "arrival"', so an agent knows this single tool covers both boards.

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?

Gives clear usage context: this is for station-level departure/arrival boards, and the type parameter selects arrivals. The note that station names accept English exonyms and fuzzy input is real operational guidance. It stops short of naming alternatives among siblings such as irail_journey or irail_train, so there is no explicit when-not guidance.

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.