Skip to main content
Glama

Irail Disturbances

irail_disturbances
Read-onlyIdempotent

Current disturbances, incidents, and planned works on the Belgian rail network (SNCB NMBS Infrabel), strikes, track works, line closures affecting Belgian train service. Returns title, summary, type (planned or disturbance), link, and last-updated time. Example: irail_disturbances({})

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": {
      "limit": 20
    },
    "name": "irail_disturbances"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax disturbances to return, 1-50 (default 15)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "limit": 20
      +  }
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the description only needs to add context, which it does by naming the returned fields (title, summary, type planned/disturbance, link, last-updated) and the data sources. It does not mention freshness guarantees beyond the last-updated field or any rate limits, keeping it short of a 5.

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?

One dense sentence front-loads the resource and scope, followed by the return fields. The trailing example call 'irail_disturbances({})' adds little because it takes no required parameters and repeats the schema.

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?

For a simple, read-only, single-optional-parameter tool with rich annotations and an explicit return-field list, the description is nearly complete. The only thing an agent might still want is freshness or guidance on what the 'planned' vs 'disturbance' type means when filtering results.

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?

The schema description coverage is 100% and the single limit parameter (range, default 15) is fully documented in the schema, so the description need not repeat it. The description does not add meaning beyond the schema, which is the baseline 3 for full coverage.

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?

The description names a specific resource and scope: current disturbances, incidents, planned works, strikes, track works and line closures on the Belgian rail network, with the data sources named (SNCB NMBS Infrabel). It is clearly distinct from the sibling journey/liveboard/train tools, which address individual trips rather than network-wide disruptions.

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?

The use case (checking network disruptions) is implied by the description, but there is no explicit statement of when to call this versus irail_journey or irail_liveboard when investigating a specific trip. No exclusions or prerequisites are given beyond the optional limit.

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.