Skip to main content
Glama

London Transport: Search stops

london-transport__stop-search
Read-onlyIdempotent

Find stations and stops by name. 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": {
      "q": "<q>"
    },
    "name": "london-transport__stop-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesName

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 declare this as a safe, idempotent, open-world read, so the safety profile is covered. The description adds genuinely useful context beyond the schema: a free-sample quota and a $0.001 USDC per-call cost via x402. It stops short of describing result limits or matching behavior.

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 tight sentences: purpose front-loaded, then the pricing caveat. Nothing is wasted and the most decision-relevant information comes first.

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?

An output schema exists so return values need no explanation, and the description covers purpose and cost. It is nearly complete for a one-parameter search, with the only gap being the matching semantics of the query (exact vs partial).

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 parameter q is documented as "Name", so the schema carries the burden. The description's "by name" merely echoes the schema without adding syntax, matching mode (prefix/fuzzy/exact), or format guidance. Baseline 3 applies.

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 (Find) and resource (stations and stops) qualified by the search mode (by name). An agent can tell it apart from a detail lookup like london-transport__stop, but it never explicitly distinguishes itself from london-transport__stops-near, which is a genuine ambiguity.

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?

"By name" implies the usage mode and contrasts implicitly with the geo-based stops-near sibling, but there is no explicit when-to-use or when-not-to-use statement and no mention of the alternative. Usage is inferable, not stated.

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