Skip to main content
Glama

TrainTrack

Hungarian train details

get_train_details
Read-onlyIdempotent

Read one observed train by trip ID, vehicle ID, or service number, including its reported position, current stop and amenities. Use trip ID if ambiguous.

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": {
      "train_id": "<train_id>"
    },
    "name": "get_train_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
train_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the meaningful qualifier 'observed', implying a valid ID for a non-observed train may return nothing, but it never elaborates on that limitation or on lookup failure behavior.

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?

A single front-loaded sentence with the resource, the accepted identifiers, the returned fields, and the disambiguation rule. No filler and nothing buried.

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 one-parameter read tool with rich annotations and no output schema, the description covers what is fetched and what comes back. Only the 'observed' scope and empty-result behavior remain under-explained.

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 0% and the schema only constrains train_id to a 1-256 char string, so the description carries the burden. It does so well by revealing that the single parameter accepts three identifier types (trip ID, vehicle ID, service number) and by recommending trip ID when ambiguous.

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 and resource ('Read one observed train') plus the fields returned (position, current stop, amenities), which separates it from list-oriented siblings like get_live_trains or search_trains. It stops short of naming an alternative explicitly, so it is clear but not fully differentiated.

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?

'Use trip ID if ambiguous' gives real guidance on identifier selection, but there is no statement of when to prefer this tool over search_trains or get_live_trains, nor any when-not condition. Usage is implied by 'one observed train' rather than spelled out.

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