Skip to main content
Glama

nearby_stops

England bus and coach stops near a point, nearest first. Pass lat and lon (WGS84), optional radius_m (1 to 2,000, default 500) and limit (1 to 50, default 10). Each stop carries its NaPTAN ATCO code id (pass it to next_departures), name, indicator (e.g. "Stop S"), locality, position, distance_m and bearing_deg from the point, and lines, the line names the Bus Open Data timetables have calling there. Bus and coach only: rail, tram, metro and ferry stops are not included, and coverage is England (plus stops just across a border that an England service calls at). Display data, never a journey plan: pass on the returned label and coverage. Requires the MapMap gateway; a deployment without the stops index answers a clear error. Display the returned attribution (NaPTAN and BODS, Open Government Licence v3.0).

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "nearby_stops"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude of the point, WGS84 degrees.
lonYesLongitude of the point, WGS84 degrees.
limitNoMost stops to return, 1 to 50 (default 10), nearest first.
radius_mNoSearch radius in metres, 1 to 2,000 (default 500).

Output Schema

NameRequiredDescriptionDefault
labelYesWhat the answer is and is not: display data, never a journey plan or an arrival prediction. Pass it on with the stops.
stopsYesStops inside the radius, nearest first.
coverageYesWhat the data covers (England bus and coach stops; no rail, tram or ferry). Pass it on with the stops.
attributionYesNaPTAN and BODS attribution (Open Government Licence v3.0): display it with the stops.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / $defs / TransitStopOut / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "lat",
      -  "lon"
      -]New value: +[
      +  "id",
      +  "name",
      +  "lat",
      +  "lon",
      +  "lines"
      +]
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: gateway dependency, defined failure mode, geographic coverage limits (England plus border stops), exclusion of other transport modes, an attribution display obligation under OGL v3.0, and a warning that this is not a journey planner.

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?

Purpose and scope are front-loaded, and nearly every clause adds information. The middle section is dense and reads as a run-on list of returned fields, and some of it duplicates the output schema, but nothing is padding.

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?

Covers the essentials for a read-only lookup: inputs, ordering, field meanings and the id handoff. However, it spends substantial space enumerating return fields that the output schema already declares, while saying nothing about result ordering edge cases or behaviour at the radius boundary, so it is thorough but partly redundant rather than fully targeted.

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 coverage is 100% and the description's parameter notes (WGS84, radius 1–2,000 default 500, limit 1–50 default 10) restate what the schema already documents. The added value is in output semantics (id usable by next_departures) rather than parameter meaning, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb, resource and scope: 'England bus and coach stops near a point, nearest first.' It also draws the boundary against rail/tram/metro/ferry and against 'nearby_places' by naming the returned ATCO code as input to 'next_departures'.

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?

Gives clear usage context: pass the returned `id` to `next_departures`, treat results as display data 'never a journey plan', and expect a clear error if the stops index is absent. It does not explicitly state when to use a different nearby-search tool, but the domain restrictions do most of that routing.

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