Skip to main content
Glama

Places along a driving route

bl_along_route
Read-onlyIdempotent

Find a specific place type—such as a gas station, restaurant, or pharmacy—along a driving route between two points, ranked by distance from the start and distance off the route.

Instructions

Find places of one kind (gas station, restaurant, pharmacy...) along the suggested driving route between two points.

Ordered by km_from_start, with off_route_km. Searches up to 12 boxes along the route, so on trips of hundreds of km places between boxes are missed; split the trip for full coverage.

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": {
      "what": "<what>",
      "from_lat": "<from_lat>",
      "from_lng": "<from_lng>",
      "to_lat": "<to_lat>",
      "to_lng": "<to_lng>"
    },
    "name": "bl_along_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatYesCategory slug from bl_categories (e.g. pharmacy, gas-station) or free text (e.g. پیتزا).
limitNoMax places to return (1-30).
to_latYesLatitude, e.g. 35.7448.
to_lngYesLongitude, e.g. 51.3753.
from_latYesLatitude, e.g. 35.7448.
from_lngYesLongitude, e.g. 51.3753.
open_nowNoOnly places open now.
max_off_route_kmNoMax distance from the road in km (0.2-3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.2.0
    • changedInput schema / properties / from_lat / description
      Previous value: -"Latitude in degrees, e.g. 35.7448."New value: +"Latitude, e.g. 35.7448."
    • changedInput schema / properties / from_lng / description
      Previous value: -"Longitude in degrees, e.g. 51.3753."New value: +"Longitude, e.g. 51.3753."
    • changedInput schema / properties / max_off_route_km / description
      Previous value: -"How far from the road a place may be, in km, e.g. 0.5 (0.2-3)."New value: +"Max distance from the road in km (0.2-3)."
    • changedInput schema / properties / open_now / description
      Previous value: -"Only places Balad marks as open right now."New value: +"Only places open now."
    • changedInput schema / properties / to_lat / description
      Previous value: -"Latitude in degrees, e.g. 35.7448."New value: +"Latitude, e.g. 35.7448."
    • changedInput schema / properties / to_lng / description
      Previous value: -"Longitude in degrees, e.g. 51.3753."New value: +"Longitude, e.g. 51.3753."
    • changedInput schema / properties / what / description
      Previous value: -"A category slug from bl_categories (e.g. pharmacy, restaurant, gas-station, atm) or free text (e.g. پیتزا, کافه)."New value: +"Category slug from bl_categories (e.g. pharmacy, gas-station) or free text (e.g. پیتزا)."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description's real contribution is the non-obvious sampling limitation: only up to 12 search boxes along the route, with gaps between boxes on long trips. It also discloses result ordering (km_from_start, off_route_km), which is genuinely useful behavior the annotations cannot convey.

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 short sentences, front-loaded with purpose, then ordering and the coverage caveat. Nothing is padded and the limitation is stated before an agent could be surprised by it.

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?

For an 8-parameter read tool with no output schema, the description covers the decisive risk (missed places between sampled boxes) and names two return fields, which is the main thing an agent needs to interpret results. It stops short of describing the full result shape or how ordering ties to distance, but no critical calling information 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%, so every parameter already carries its own documentation, and the description adds little beyond echoing that 'what' is a category or free text. The implied off-route constraint and the radius default are already in the schema, 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?

The description gives a specific verb and resource — 'Find places of one kind ... along the suggested driving route between two points' — and the 'along a route' framing cleanly separates it from siblings like bl_nearby and bl_search, which are point- or query-based.

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?

It scopes usage to a single category/text value and prescribes a workaround ('split the trip for full coverage') for long journeys, which is real guidance. However, it never states when to prefer a sibling (e.g. bl_nearby or bl_search) over this tool, so alternative selection is left to inference.

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