Skip to main content
Glama

get_nearest_bus_stop

Read-onlyIdempotent

Find the nearest Straeto public bus stops to a given location.

Returns stop name, stop_id, distance in metres, and routes serving each stop.
Each stop contains latitude and longitude — render all stops as markers on a
map alongside the user's search location. Use the returned stop_id in get_bus_schedule.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_nearest_bus_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYesWGS84 latitude of the location to search from.
longitudeYesWGS84 longitude of the location to search from.
max_resultsNoMaximum number of stops to return (1–10).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, non-open-world), so the description only needs to add context — and it does, by disclosing the returned fields (name, stop_id, distance, routes, coordinates) and stating an intended presentation action. No rate limits, pagination, or error behavior are mentioned, so it is not a 5.

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?

Three short, front-loaded sentences: capability first, return shape second, chaining third. The map-rendering instruction is arguably prescriptive of downstream UI behavior rather than tool semantics, but it is brief and does not bloat the definition.

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, yet the description still enumerates the useful return fields and the intended next call, which is more than sufficient for a 3-parameter read tool. The only gap is the absence of any note on how distance ordering or an empty result behaves.

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%: latitude, longitude, and max_results all carry their own descriptions and bounds, so the schema does the heavy lifting. The description only implicitly frames 'a given location' and adds no format or defaulting detail beyond the schema, which is the baseline 3.

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 and resource ('Find the nearest Straeto public bus stops to a given location'), names the provider, and distinguishes it from schedule/route lookups by pointing to get_bus_schedule as the follow-up. An agent can tell exactly what this returns without opening the schema.

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 chaining guidance ('Use the returned stop_id in get_bus_schedule') and frames the call around a user search location, so the agent knows when to reach for it. It stops short of naming alternatives or exclusions (e.g., when to use a route search instead), which keeps it below a 5.

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