Skip to main content
Glama

Irail Journey

irail_journey
Read-onlyIdempotent

Plan a train journey between two Belgian stations, SNCB NMBS route planner with legs, transfers, live delays, and platforms per leg. Answers "next train from Brussels to Antwerp", "how do I get from Ghent to Liège by rail". Optional depart_at or arrive_by as ISO datetime ("2026-07-20T09:00") or time ("09:00"), interpreted in Belgian local time. Example: irail_journey({ from: "Brussels-South", to: "Antwerp-Central" })

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": {
      "to": "Antwerp-Central",
      "from": "Brussels-South"
    },
    "name": "irail_journey"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination station, e.g. "Antwerp-Central"
fromYesOrigin station, e.g. "Brussels-South"
limitNoMax connections to return, 1-6 (default 4)
arrive_byNoArrive by this time instead, same formats as depart_at. Overrides depart_at
depart_atNoDepart at/after this time, "YYYY-MM-DDTHH:MM" or "HH:MM" (today), Belgian local time. Default: now

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / arrive_by / description
      Previous value: -"Arrive by this time instead — same formats as depart_at. Overrides depart_at"New value: +"Arrive by this time instead, same formats as depart_at. Overrides depart_at"
    • changedInput schema / properties / depart_at / description
      Previous value: -"Depart at/after this time — \"YYYY-MM-DDTHH:MM\" or \"HH:MM\" (today), Belgian local time. Default: now"New value: +"Depart at/after this time, \"YYYY-MM-DDTHH:MM\" or \"HH:MM\" (today), Belgian local time. Default: now"
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "from": "Brussels-South",
      +    "to": "Antwerp-Central"
      +  },
      +  {
      +    "depart_at": "09:30",
      +    "from": "Ghent-Sint-Pieters",
      +    "limit": 3,
      +    "to": "Liège-Guillemins"
      +  }
      +]
  3. First observed

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, non-destructive, so the safety profile is covered. The description adds genuinely new behavior: results include live delays and per-leg platforms, times are interpreted in Belgian local time, depart_at defaults to now, and arrive_by takes precedence over depart_at.

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?

Three sentences, front-loaded with the core purpose, then time semantics, then a single compact example call. No filler or marketing language; every sentence carries usable information.

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 compensates by enumerating what a result contains (legs, transfers, delays, platforms). Missing only guidance on failure cases such as unknown or international station names and a rough sense of result volume beyond the limit param.

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% and the schema already documents formats, defaults, the 1-6 limit range, and the arrive_by override, so the description mostly restates it. The Belgian-local-time interpretation is the one piece of added meaning, which is not enough to exceed the baseline.

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?

States a specific verb and resource ('Plan a train journey between two Belgian stations') plus the payload returned (legs, transfers, live delays, platforms per leg), which separates it in spirit from a departure board or single-train lookup. It never names the sibling route/liveboard/train tools, so the differentiation is implied rather than explicit.

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?

Concrete trigger phrasing is supplied — 'next train from Brussels to Antwerp' and 'how do I get from Ghent to Liège by rail' — making it clear this is the point-to-point route planner. It stops short of saying when NOT to use it or which sibling to pick for departures, live delays alone, or disruptions.

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.