Skip to main content
Glama

Train stops

mb_train_stops
Read-onlyIdempotent

Fetch the ordered list of stops a train makes, with dates and local times, using a class_id from search results. See all stations, including stops before your boarding point, to plan your journey.

Instructions

Every station a train stops at, in order, with the date and local time at each.

Takes a class_id, never a train number. The first stop can be before your station.

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": {
      "class_id": "<class_id>"
    },
    "name": "mb_train_stops"
  }
}

Input Schema

NameRequiredDescriptionDefault
class_idYesclass_id from a fresh mb_search_trains result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • changedInput schema / properties / class_id / description
      Previous value: -"class_id of a train class from a fresh mb_search_trains result, e.g. 9847134."New value: +"class_id from a fresh mb_search_trains result."
    • removedInput schema / title
      Removed value: -"mb_train_stopsArguments"
  2. Changed2 schema fields changedv0.3.0
    • removedInput schema / properties / class_id / title
      Removed value: -"Class Id"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "mb_train_stopsDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds useful behavioral detail: results are ordered, carry date and local time, and may begin before the queried station — a real expectation-setting warning. No pagination or size limits mentioned.

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?

Two short sentences, both earning their place: the first defines the output, the second prevents the most likely input mistake. Front-loaded with zero filler.

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 a single parameter, full schema coverage, and no output schema, the description adequately conveys returns and the key caveat about leading stops. It doesn't address result size or failure modes, but nothing essential for a correct call is missing.

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% and already documents class_id's origin, so the baseline is 3. The description goes slightly beyond by clarifying what the parameter is not ('never a train number') and implying the value must be freshly obtained, which helps prevent misuse.

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+resource: it enumerates every station a train stops at, in order, with date and local time. The line 'Takes a class_id, never a train number' distinguishes it from train-search style tools, though it doesn't name the sibling that supplies class_id.

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?

Usage is implied rather than spelled out: you must already have a class_id (freshness noted) and it warns that the first stop can precede your station. It never explicitly says when to call this versus mb_search_trains or mb_alternative_routes.

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