Skip to main content
Glama

Bus stops nearby

bus_stops_nearby
Read-only

Find bus stops nearest a latitude and longitude, returning each stop's heading and city bus and InterCity coach routes. Use the stop and route with bus_eta to get live arrivals.

Instructions

Bus stops nearest to a coordinate, each with its heading and the city bus and InterCity coach routes that stop there, nearest first. Pass a stop and route to bus_eta for live arrivals. Example: lat 25.0478, lon 121.517, city "Taipei".

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>",
      "city": "<city>"
    },
    "name": "bus_stops_nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude (WGS84), e.g. 25.0478.
lonYesLongitude (WGS84), e.g. 121.517.
cityYesCity the point is in: a TDX code (Taipei, NewTaipei, Taoyuan, Taichung, Tainan, Kaohsiung, Keelung, Hsinchu, HsinchuCounty, MiaoliCounty, ChanghuaCounty, NantouCounty, YunlinCounty, ChiayiCounty, Chiayi, PingtungCounty, YilanCounty, HualienCounty, TaitungCounty, KinmenCounty, PenghuCounty, LienchiangCounty) or its Chinese name (臺北市, 新北市, ...). InterCity coach stops are always included.
limitNoMaximum number of stops to return (default 10).
radiusMetersNoSearch radius in metres (default 300).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower; the description adds real value by disclosing result ordering (nearest first), what each result contains, and the useful quirk that InterCity coach stops are always included. It doesn't cover behavior at radius/limit boundaries or whether an empty result is possible.

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?

Three compact sentences with the core purpose front-loaded, followed by the handoff tool and a concrete example. No redundant restatement of the title.

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 does the right thing by sketching the return shape (stops with heading and routes, ordered nearest first). The remaining gap — no mention of limit/radius defaults or result truncation — is covered by the schema, so nothing critical is missing.

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 every parameter is documented with ranges, defaults and a city-code enumeration, so the schema carries the load. The description only restates the coordinate idea and adds an example lat/lon pair, which the schema already supplies as examples.

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?

States a specific verb/resource ('Bus stops nearest to a coordinate') plus the payload contents (heading, city bus and InterCity coach routes), which cleanly separates it from geo-siblings like parking_nearby, youbike_nearby and ev_charger_nearby. Nearest-first ordering is also declared.

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 an explicit follow-on path — pass a stop and route to bus_eta for live arrivals — which tells the agent where this tool sits in a workflow. It does not state when to prefer a sibling like bus_route_stops or bus_stop_arrivals instead, so it stops short of full routing guidance.

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