Skip to main content
Glama
Sign In
irail-mcp

irail-mcp

by HansF
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_stations

Search for railway stations in Belgium by name. Enter a station name or partial name to get matching results for route planning and departures.

Instructions

Search for railway stations in Belgium by name

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": {
      "query": "<query>"
    },
    "name": "search_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage code (en, nl, fr, de, it)en
queryYesStation name or partial name to search for (e.g., 'Brussels', 'Antwerp')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, and description only states search purpose without detailing behavioral traits like maximum results, pagination, authentication needs, or rate limits. Minimal behavioral disclosure.

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?

Single short sentence with no extraneous information. Front-loaded and efficient.

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

Completeness3/5

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

For a simple search tool with no output schema, description is adequate but could include more details about result format, partial match behavior, or language usage. Not complete but functional.

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 covers 100% of parameters with descriptions. The description adds 'by name' context but does not significantly enhance parameter understanding beyond the schema. Baseline score of 3 is appropriate.

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?

Description clearly states 'Search for railway stations in Belgium by name', providing a specific verb, resource, and scope. It distinguishes from sibling tools which focus on connections, disturbances, liveboard, and train info.

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?

Purpose is clear, but no explicit guidance on when to use this tool versus siblings. No 'when not to use' or alternative tool mentioned. Usage is implied but not stated.

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