Skip to main content
Glama

London Transport: Line status

london-transport__line-status
Read-onlyIdempotent

Live status and disruption for one line. A few free samples a day, then $0.001 USDC per call via x402.

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": {
      "line": "<line>"
    },
    "name": "london-transport__line-status"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineYesLine id, e.g. "victoria", "elizabeth", "northern"

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description adds genuinely non-structural behavioral context: a metered pay-per-call model with a few free daily samples and $0.001 USDC via x402, which affects how an agent should budget calls.

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 sentences, zero filler, front-loaded with the purpose and followed by the cost constraint. Every clause (scope, cost, payment rail) earns its place.

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 an output schema present, return values need not be described, and annotations cover the safety profile. Purpose, scope, and the unusual payment requirement are all covered; only error behavior for an invalid line id is unaddressed.

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% and the single 'line' parameter already documents format with examples ('victoria', 'elizabeth', 'northern'). The description only adds the implied constraint that exactly one line is queried; baseline 3 is correct when the schema carries the parameter detail.

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+resource ('Live status and disruption') and scopes it to 'one line', which implicitly separates it from siblings like tube-status and mode-status that cover multiple lines or a whole mode. It stops short of naming those alternatives, so sibling differentiation is inferential rather than explicit.

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 single-line scope implies when this tool is appropriate versus the broader tube-status/mode-status tools, but no when-to-use or when-not-to-use guidance is stated. The pricing note is present but is not routing guidance.

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