Skip to main content
Glama
Sign In
irail-mcp

irail-mcp

by HansF
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_train_info

Retrieve detailed information for a specific train, including all stops and current delays.

Instructions

Get detailed information about a specific train including all stops and current delays

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": {
      "train_id": "<train_id>"
    },
    "name": "get_train_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate in format YYYY-MM-DD (default: today)
langNoLanguage code (en, nl, fr, de, it)en
train_idYesTrain ID from liveboard results (e.g., 'IC1234' or 'BE.NMBS.IC1234')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates the tool provides detailed info including stops and delays, suggesting real-time or schedule data, but does not disclose data freshness, required permissions, rate limits, or any side effects. The parameter description hints at input format, but behavioral traits beyond the basic operation are absent.

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?

The description is a single, front-loaded sentence (14 words) that efficiently conveys the core purpose without any extraneous information.

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

Completeness2/5

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

Given the absence of an output schema and annotations, the description is insufficient. It does not specify the return format (e.g., list of stops, delay structure), data source, or update frequency. For a tool with moderate complexity (stops and delays), the description lacks context needed for an agent to fully understand the tool's capabilities.

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% with all three parameters described in the schema. The description does not add any additional meaning for the parameters beyond what the schema already provides. The output hint about 'stops and current delays' is about return values, not parameter semantics.

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 clearly states the tool retrieves detailed information about a specific train, including stops and current delays. It uses a specific verb ('Get') and resource ('train'), and distinguishes from sibling tools like get_liveboard (station-based) and get_disturbances (general disruptions).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide guidance on when to use this tool versus alternatives, nor does it mention prerequisites (e.g., obtaining a train_id from get_liveboard). No when-not or exclusionary advice is given.

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

Deploy Server

Other Tools