Skip to main content
Glama

TrainTrack

Search Hungarian trains

search_trains
Read-onlyIdempotent

Find observed trains by service, station, destination, class, or amenity. This is not itinerary or ticket availability.

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": "search_trains"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
originNo
amenityNo
train_typeNo
destinationNo
search_typeNo
bounding_boxNo
delayed_onlyNo
service_classNo
train_categoryNo
min_delay_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the meaningful nuance that results are “observed” trains rather than scheduled itineraries, but it says nothing about result volume, pagination, or how the limit interacts with the open-world query.

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, front-loaded with the primary capability, with zero filler. The exclusion sentence is the only addition and it earns its place by blocking a wrong assumption.

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?

A 12-parameter, zero-required, open-world search with a nested bounding_box and no output schema needs far more explanation than two sentences. Nothing tells an agent how to combine facets, whether omitted filters mean 'all', or what comes back, leaving the definition inadequate for the tool's complexity.

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 12 parameters, so the description must carry the burden and it does not. It implies origin/destination, class, amenity and train-type filtering, but leaves limit, query, search_type, train_category, bounding_box, delayed_only and min_delay_minutes completely unexplained, including how search_type interacts with which other fields.

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 description gives a specific verb and resource ("Find observed trains") plus the facets it can be filtered by (service, station, destination, class, amenity). The added "not itinerary or ticket availability" narrows scope usefully, though it never names a sibling such as get_live_trains or get_most_delayed_trains, so differentiation is left implicit.

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?

It supplies one clear exclusion (“not itinerary or ticket availability”), which tells an agent what this tool is not for. However, there is no positive guidance on when to prefer this over the adjacent lookups get_live_trains, get_most_delayed_trains, or get_train_details, so the routing decision is largely inferred.

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