Skip to main content
Glama

TrainTrack

Hungarian live trains

get_live_trains
Read-onlyIdempotent

List observed trains by category, amenity, place, delay, or map bounds. Returns freshness and coordinates when known.

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_live_trains"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
originNo
amenityNo
train_typeNo
destinationNo
bounding_boxNo
delayed_onlyNo
service_classNo
train_categoryNo
min_delay_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds a useful return hint ('freshness and coordinates when known'), but omits defaults (e.g. what happens if limit is omitted), pagination/truncation behavior at the 500 cap, and whether results are ordered by delay or departure.

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?

Two sentences, front-loaded with the core purpose and the filter dimensions, with no filler. It is efficient, though arguably too terse for a ten-parameter tool with a nested object.

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 10 undocumented parameters, an undocumented nested object, and no output schema, the description is far from complete enough to call the tool confidently. Key operational details (defaults, filter interaction, result ordering) are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 10 parameters, including a nested bounding_box object, so the description must carry the semantic load. It partially maps facets to parameters, but the word 'category' ambiguously covers train_category, train_type and service_class, and limit, min_delay_minutes, delayed_only and the bounding box coordinate order are never explained.

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?

The definition uses a specific verb and resource ('List observed trains') and enumerates the filter facets (category, amenity, place, delay, map bounds), which clearly signals a filtered listing tool. It never names a sibling such as get_most_delayed_trains or search_trains, so differentiation is left to inference.

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?

There is no when-to-use guidance and no exclusion criteria: nothing says when to prefer this over search_trains or get_most_delayed_trains, nor whether filters combine (AND vs OR). The agent must infer usage entirely from the facet list.

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