Keep Dawdling

next_train

Read-onlyIdempotent

Next listed eligible cached train from one catalogue station to another, terminating or calling there. No journey planning or completeness guarantee.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "next_train"
  }
}

Input Schema

Name	Required	Description	Default
`to`	Yes	Supported station CRS, slug or catalogue name. Call list_stations for the finite catalogue.
`from`	Yes	Supported station CRS, slug or catalogue name. Call list_stations for the finite catalogue.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent and open-world behavior, so the bar is lower. The description still adds real context the annotations don't: results come from a cached/listed feed, are not guaranteed complete, and include trains that terminate at the destination rather than only through-services. It stops short of saying how fresh the cache is.

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 with zero filler: the core behavior comes first and the disclaimers are compressed into one clause. Nothing could be removed without losing information.

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?

With no output schema, the description should say what a result contains (departure time, service, platform, terminating flag). It hints at terminating trains but never describes the returned fields, and the meaning of 'cached' staleness is left undefined.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented with accepted formats and a pointer to list_stations. The description's 'one catalogue station to another' only echoes the catalogue constraint, adding no syntax, aliasing or normalization detail beyond the schema.

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: returns the next listed train from one catalogue station to another, with the qualifier that the train terminates or calls at the destination. This is enough to tell it apart from get_departures and platform_for, though the dense phrasing ('next listed eligible cached train') takes a moment to parse.

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?

The closing clause 'No journey planning or completeness guarantee' sets a negative boundary, which is useful. However, it never names get_departures or list_stations as the alternatives for broader departure lists or station validation, so the agent must infer the routing itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Keep Dawdling tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?