Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_train_departures_db

Query live Deutsche Bahn (DB IRIS-TTS) train departures, ICE/IC/RE lines, platforms, and real-time delay minutes for any German train station.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_train_departures_db"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationNoGerman railway station name (e.g. Berlin Hbf, München Hbf, Köln Hbf, Frankfurt Hbf)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully reveals that data is 'live' and includes real-time delays, but it omits whether an API key or authorization is needed, rate limits, behavior for unknown stations, and what happens when the station argument is omitted (the schema marks it non-required).

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?

One front-loaded sentence that leads with the verb and data source, then enumerates returned fields and scope. Nothing is redundant or padded.

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 one-parameter read tool with no output schema, the description adequately conveys what comes back (departures, lines, platforms, delay minutes) and the data source. The remaining gap is the undefined behavior when the optional station argument is absent.

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 single parameter has 100% schema description coverage with example station names, so the schema does the heavy lifting. The description only adds the constraint that any German station is acceptable, which is marginal beyond the schema's own examples.

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 verb and resource ('Query live Deutsche Bahn (DB IRIS-TTS) train departures') plus the concrete returned fields (lines, platforms, delay minutes) and the geographic scope ('any German train station'). None of the siblings touch rail data, so the purpose is unambiguous at a glance.

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?

'for any German train station' implicitly signals the usage context, but there is no explicit when-to-use, no exclusions, and no note on what to do for non-German or ambiguous station names. An agent must infer the invocation conditions.

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.

Resources