Skip to main content
Glama

List stations

list_stations
Read-onlyIdempotent

Lists the stations covered, whether each is live, and its platform range. Use it first when the person asks about a station other than Euston. It does not return departures. Read only. Predictions are unofficial and may be wrong. Station screens are the official source.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 "Read only" is pure repetition. The genuinely additive content is the trust caveat: "Predictions are unofficial and may be wrong. Station screens are the official source" — useful data-quality context an agent cannot get from structured fields. It does not describe list size, ordering, or whether the station set is fixed, leaving some behavioral ground uncovered.

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?

The capability is front-loaded in the first sentence and the whole definition is five short sentences with no filler. The only weak line is the redundant "Read only", and the staccato one-clause-per-sentence style reads slightly like a list of fragments rather than flowing guidance.

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?

With no output schema, the description carries the burden of describing returns, and it does name the returned fields (stations, live flag, platform range) plus the no-departures exclusion. The accuracy disclaimer further covers expectations. What is missing is any sense of shape or scale of the result (ordering, completeness), which a no-parameter enumeration tool would benefit from.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not waste words restating an empty 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?

The description gives a specific verb and resource ("Lists the stations covered") and even enumerates the returned attributes: live status and platform range. It also carves out a boundary against get_departures with "It does not return departures", so an agent can distinguish it from at least one sibling, though the other siblings (find_train, get_train, get_track_record) are never positioned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete trigger condition: "Use it first when the person asks about a station other than Euston", which tells the agent when this is the entry point rather than a follow-up. It stops short of naming the alternative tool to use for Euston or for departure lookups, so the routing is clear in one direction only.

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