Skip to main content
Glama

Driving route with live traffic

bl_route
Read-onlyIdempotent

Plan driving routes in Iran with distance, current-traffic travel time, tolls, road details, traffic-zone warnings, up to 3 alternatives, and optional stops or turn-by-turn steps.

Instructions

Get driving routes in Iran with distance, travel time in current traffic, tolls, roads and traffic-zone warnings.

Up to 3 routes, suggested first; notes are the site's labels (delay, toll in Toman); traffic_plan appears when a route enters a restricted zone (طرح ترافیک, زوج و فرد); legs with stops. Driving only. Get coordinates from bl_search. 'No route': a point is outside Iran or off the road network.

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

Input Schema

NameRequiredDescriptionDefault
stepsNoInclude turn-by-turn steps.
stopsNoStops in order, each "lat,lng" (max 3).
to_latYesLatitude, e.g. 35.7448.
to_lngYesLongitude, e.g. 51.3753.
from_latYesLatitude, e.g. 35.7448.
from_lngYesLongitude, e.g. 51.3753.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 / steps / description
      Previous value: -"Include turn-by-turn steps of the suggested route."New value: +"Include turn-by-turn steps."
    • changedInput schema / properties / stops / description
      Previous value: -"Stops on the way, in order, each \"lat,lng\", e.g. [\"35.7016,51.4206\"] (max 3)."New value: +"Stops in order, each \"lat,lng\" (max 3)."
    • 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."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description earns credit for what it adds: response cardinality (up to 3 routes, suggested first), field semantics (`notes` are site labels with delay and toll in Toman, `traffic_plan` appears only when entering a restricted zone), and an explicit failure mode. It does not discuss latency, whether traffic data is cached versus live, or how stop ordering affects the returned legs.

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?

Front-loads the core capability, then uses a compact semicolon-separated glossary for response fields, ending with the failure case. Everything earns its place, though the backtick field glossary and mixed Persian/English terms make it denser to parse than a fully plain-prose version would be.

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?

With no output schema, the description carries the burden of explaining returns and does so for a six-parameter routing tool: route count and ordering, cost/label fields, restricted-zone plans, legs and stops, plus the empty-result condition. An agent has enough to call this correctly and interpret the response without further documentation.

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 including `steps`, `stops` (with pattern and max 3) and the bounded lat/lng values is already documented in the schema. The description adds nothing about parameters beyond touching on `stops` indirectly through `legs`; it does not explain the effect of `steps` on the response or how intermediate stops interact with the suggested route. Baseline 3 is appropriate.

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 (driving routes) with the geographic scope (Iran) and the return content (distance, travel time in current traffic, tolls, roads, traffic-zone warnings). An agent can tell this apart from bl_search (coordinate lookup) and from bl_along_route/bl_nearest_by_drive based on the 'Driving only' constraint and the full origin-destination framing.

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: coordinates must come from bl_search, driving is the only mode, and the 'No route' failure condition (point outside Iran or off the road network) tells the agent when to expect empty results. It stops short of explicitly contrasting with siblings like bl_nearest_by_drive or bl_along_route, and gives no guidance on when to request steps or stops.

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