Skip to main content
Glama

Places along a route

places_along_route
Read-onlyIdempotent

Find stops on the way between two locations, filtering by category or name, and see detour distance and route position for each.

Instructions

Places on the way from A to B: corridor search along the route.

Answers "find a coffee shop on my drive to the airport" — the route tool
plus find_places in one call. Builds the same street-graph shortest path
`route` returns, then finds places whose nearest point on that path is
within max_detour_m (default 1000m, capped at 5000m; larger values
return a bad_request error rather than being silently clamped).

Each result row is a find_places row plus two numbers: detour_m, the
straight-line distance to the route doubled — an approximation of the
round trip off and back on, not a re-routed detour — and along_m, how
far along the route from the origin that place sits, so "roughly
halfway" is answerable. Results are ordered by along_m (route order,
reading as an itinerary) rather than by detour cost. When more than
limit places are on the way, the response is an even sample spanning the
whole route — never just the first limit, which would drop the far end
of the journey — and carries "truncated": true saying so. It also
carries {"route": {"distance_m", "duration_s", "mode"}} for the
underlying route. A composed itinerary also carries
verify_before_going when any stop is low-confidence or listed closed,
naming the 1–2 places most worth checking.

category and name narrow the search exactly as they do in find_places
(category matches Overture's taxonomy, e.g. 'coffee_shop'; name is a
substring match) — worth passing on a long route, since an unfiltered
corridor through a dense area can hold more places than the search
considers, in which case the response carries "truncated": true and a
note saying so.

Omit mode to use the stored preferences mode, else drive. Same cost model
and the same straight-line-distance caps as `route`, and the same
structured errors: route_too_long, no_graph_nearby, no_route,
unsupported_mode, and bad_request for non-finite/out-of-range
coordinates or an invalid max_detour_m.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoTravel mode. Default: stored preference, else drive.
nameNo
limitNo
to_latYes
to_lonYes
categoryNo
from_latYes
from_lonYes
max_detour_mNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

A5/5.0
Behavior5/5

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

With annotations already declaring read-only, idempotent, and non-destructive hints, the description adds substantial behavioral context: results are ordered by along_m rather than detour cost, the detour_m metric is an approximation rather than a re-routed detour, results are evenly sampled when truncated, and a composed itinerary carries verify_before_going. This is far beyond the annotation baseline and meaningfully informs invocation and result interpretation.

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?

The description is long but every sentence earns its place, covering purpose, filtering, output fields, ordering, truncation, route metadata, and error behavior. It is front-loaded with the core concept, then branches into increasingly specific details, making it dense yet scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, parameter count, and the availability of an output schema, the description covers all the non-obvious aspects an agent needs: result row structure, ordering semantics, sampling behavior, route metadata, composed-itinerary verification, mode resolution, and error cases. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 11%, but the description thoroughly compensates by explaining max_detour_m's default, cap, and error behavior; category and name semantics matching find_places; mode's default-to-stored-preferences behavior; and limit's effect on sampling/truncation. Even the coordinate parameters are implicitly clear from the 'from A to B' framing and the route context.

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?

The description uses a specific verb phrase 'corridor search along the route' and explicitly answers an example query, making the tool's function immediately clear. It also distinguishes itself from sibling tools by describing itself as 'the route tool plus find_places in one call,' so an agent can tell it apart from both without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use the tool: when the need is 'places on the way from A to B,' and it names the constituent siblings (route and find_places) without being either one alone. It also provides practical guidance on when to pass filters ('worth passing on a long route') and how mode selection behaves, giving an agent actionable selection criteria.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chuofringer/placeroot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server