Skip to main content
Glama

TrainTrack

Most delayed observed trains

get_most_delayed_trains
Read-onlyIdempotent

Rank non-cancelled trains with a reported delay, longest delay first.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
min_delayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds genuinely new behavioral context about what is included (cancelled trains excluded, only trains with a reported delay) and the ordering, but says nothing about result volume, pagination, or how ties are broken.

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 zero filler; the selection rule and ordering come first and nothing is restated from the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity, two-parameter read tool with no output schema, the description covers the selection and ordering logic adequately. It is still incomplete on the two inputs it exposes, leaving units and the meaning of the result cap ambiguous for an agent trying to call it correctly.

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 carries the full burden for both parameters, yet it never explains that min_delay is a threshold in minutes (default 5, max 1440) or what limit controls. The phrase 'reported delay' gestures at a delay filter but adds no usable meaning beyond the raw schema types.

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 ('Rank ... trains') plus the exact selection criteria (non-cancelled, reported delay) and sort order ('longest delay first'). That is far more precise than the title alone and clearly distinguishes it from a plain live-trains or search tool, though it never names a sibling to contrast with.

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 or when-not-to-use guidance and no pointer to alternatives such as get_delay_statistics or search_trains. Usage must be inferred entirely from the filtering criteria embedded in the sentence.

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