Skip to main content
Glama

Irail Train

irail_train
Read-onlyIdempotent

Track one Belgian train by its number, is my Belgian train delayed. All stops with scheduled vs actual times, per-stop delay in minutes, platforms, current delay, and live position. Accepts "IC 1832", "IC1832", or "BE.NMBS.IC1832". Train numbers come from irail_liveboard or irail_journey. Example: irail_train({ id: "IC1832" })

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": {
      "id": "IC1832"
    },
    "name": "irail_train"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTrain id, e.g. "IC1832", "IC 538", "S52558", "EUR9381", or "BE.NMBS.IC1832"
dateNoOptional travel date "YYYY-MM-DD" (default today, Belgian time)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "id": "IC1832"
      +  },
      +  {
      +    "date": "2026-07-20",
      +    "id": "S52558"
      +  }
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior3/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 by structured data. The description earns credit for describing the payload shape — per-stop scheduled vs actual times, delay per stop, platforms, live position — which annotations cannot convey. It does not cover failure behavior (invalid train number, out-of-range date, no service on that day), so the behavioral picture is incomplete rather than wrong.

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?

Front-loaded with the identification clause and the return contents, then formats, provenance, and an example — a sensible ordering with no filler. The mid-sentence "is my Belgian train delayed" reads as a copied user query and is redundant with the surrounding content, slightly hurting flow without costing 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 takes on the job of enumerating returned fields, and it does so concretely enough that an agent knows what to expect. The accepted ID formats reinforce the 100%-covered schema. Missing only edge-case behavior and any indication of what happens when a train is not found.

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 baseline is 3, but the description adds meaning the schema does not: it names the accepted format variants ("IC 1832", "IC1832", "BE.NMBS.IC1832") as equivalent inputs, signaling the tool normalizes spacing and prefixes. The optional date parameter is left entirely to the schema, which is adequate but unmentioned in the prose.

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 with scope: "Track one Belgian train by its number", and immediately enumerates what the response contains (all stops, scheduled vs actual, platforms, current delay, live position). That is far more concrete than a restated title. It stops short of a full 5 because the relationship to siblings is described only as ID provenance ("Train numbers come from irail_liveboard or irail_journey"), not as an explicit use-case distinction.

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 agent is told the precondition (you need a train number) and where to get one, plus a worked call example, which is enough to know when this tool applies. It gives no explicit exclusions — there is no statement about when to prefer irail_liveboard or irail_journey instead, or what happens if the ID is unknown.

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.