Skip to main content
Glama

TrainTrack

Hungarian rail delay statistics

get_delay_statistics
Read-onlyIdempotent

Summarize delay buckets and groups for the current observation sample. Unknown delay and cancellations are reported separately.

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

Input Schema

NameRequiredDescriptionDefault
group_byNo
timeframeNo

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 readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that unknown delay and cancellations are reported separately rather than folded into buckets — but says nothing about the shape of the aggregates, counts, or ordering of results.

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 tight sentences with the core operation front-loaded and no filler. The economy is appropriate for the tool's simplicity, though the brevity comes at the cost of the parameter detail that would make it more actionable.

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?

With no output schema and 0% parameter description coverage, the description bears the full burden and does not meet it: an agent cannot learn what a 'bucket' is, how grouping affects the result, or how to choose between train_type and route. For a two-parameter aggregation tool this leaves meaningful gaps.

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%, so the description must carry parameter meaning, and it largely fails: the word 'groups' only faintly hints at the group_by parameter, and the enum values (train_type vs route) are never explained or distinguished. The timeframe constant ('current') is echoed by 'current observation sample' but never clarified as a fixed value.

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 names a specific verb+resource combination ('Summarize delay buckets and groups') scoped to 'the current observation sample,' which an agent can map to an aggregate statistics tool. It does not, however, distinguish itself from siblings like get_network_stats or get_most_delayed_trains, so the agent must infer which aggregate tool is appropriate.

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 explicit when-to-use guidance and no mention of alternatives, even though several sibling tools (get_network_stats, get_most_delayed_trains) plausibly overlap. The only usage signal is the implicit 'current observation sample' scoping, which the agent must interpret on its own.

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