Skip to main content
Glama

directions

Read-onlyIdempotent

Generate routes, ETAs, and turn-by-turn directions between locations. Live traffic is post-route ETA enrichment and does not change the returned path (path_influenced=false); truck traffic adjustments are slowdown-only. Supports car / truck / motorcycle / pedestrian / bicycle, with hazmat + dimension + toll avoidance for commercial routing. ETAs are returned as ISO 8601 with timezone offset (in the destination's local timezone). Use vehicle_profile presets (10 total — DRY_VAN_53, FLATBED_48/_40, STEP_DECK, TANKER, BOX_TRUCK_26, AUTO_CARRIER, SPRINTER_VAN, DOUBLE_TRAILER, OVERSIZE) when routing trucks — they set height/weight/length in one parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesDestination: address string ('Houston, TX'), 'lat,lon' string, or { lat, lon } object
viaNoIntermediate stops in order; same shape as from/to. Up to 48 waypoints (max 50 total locations).
fromYesOrigin: address string ('Houston, TX'), 'lat,lon' string, or { lat, lon } object
unitsNoDistance units (default: miles). Accepts 'km'/'mi' as aliases.
hazmatNoSet true when transporting hazardous materials to avoid restricted routes
costingNoTransport mode (default: auto). Use 'truck' for commercial vehicles
axle_loadNoAxle weight in metric tons (e.g. 9.07t = 20,000 lbs per axle)
top_speedNoMaximum speed in km/h (default 105 for trucks)
use_ferryNoFerry preference 0-1 (0=avoid, 1=allow)
alternatesNoNumber of genuine motorized alternate routes to request (0, 1, or 2). Positive values require no via waypoints.
axle_countNoNumber of axles (default 5 for semi-trailer)
avoid_tollsNoAvoid toll roads when user requests toll-free routing
truck_widthNoTruck width in meters (e.g. 2.6m = 8'6")
truck_heightNoTruck height in meters (e.g. 4.11m = 13'6"). Triggers bridge avoidance
truck_lengthNoTruck length in meters (e.g. 16.2m = 53')
truck_weightNoTruck weight in metric tons (e.g. 36.3t = 80,000 lbs). Triggers weight-restricted road avoidance
use_highwaysNoHighway preference 0-1 (0=avoid, 1=prefer)
include_trafficNoApply post-route live-traffic ETA enrichment (default: true). Traffic does not change the returned path; truck adjustments are slowdown-only.
vehicle_profileNoPreset vehicle profile (10): DRY_VAN_53, FLATBED_48, FLATBED_40, STEP_DECK, TANKER, BOX_TRUCK_26, AUTO_CARRIER, SPRINTER_VAN, DOUBLE_TRAILER, OVERSIZE. Each sets height/weight/length/axle_count for that vehicle class in one parameter (e.g. DRY_VAN_53 = 4.11m tall, 36.3t, 22.25m long, 5 axles; OVERSIZE = 4.88m tall, 3.66m wide, 45.36t). The response echoes the applied dims in costing_options.truck. Any individual truck_height/truck_weight/etc. overrides a single field.
include_geometryNoRoute geometry shape control. "none" returns origin/destination Points only. "encoded" returns an encoded polyline6 string in a top-level `geometry` field plus origin/destination Points (≈95% smaller than raw GeoJSON; decode with @mapbox/polyline at precision 6). "full" emits decoded coordinates as a LineString in `geojson.features[0]`. When omitted (default), small routes use "full" and long routes auto-downgrade to "encoded" with a `geometry_truncated` warning.
include_elevationNoWhen true, include available route elevation fields. Point elevation may be returned for the origin and destination. Cumulative gain/loss is returned only when route-profile elevation is available.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNo
geojsonNo
metricsNo
summaryNoMap of scalar facts the LLM should surface verbatim
alternatesNo
display_hintNo
timezone_endNo
traffic_routeNo
timezone_startNo
costing_optionsNo
elevation_end_mNo
base_arrival_utcYesArrival time derived from the base duration, expressed as an ISO 8601 UTC timestamp.
elevation_end_ftNo
elevation_gain_mNo
elevation_loss_mNo
elevation_gain_ftNo
elevation_loss_ftNo
elevation_start_mNo
base_arrival_localYesArrival time derived from the base duration in the destination's local time, or null when the local timezone is unavailable.
elevation_start_ftNo
traffic_provenanceYes
base_duration_secondsYesRoute duration before any traffic-based adjustment, in seconds.
effective_arrival_utcYesAuthoritative arrival time for this response, expressed as an ISO 8601 UTC timestamp.
traffic_delay_secondsYesEffective duration minus base duration, in seconds. Positive means traffic made the ETA slower, negative means it made the ETA faster, and zero means the duration was unchanged. For truck costing, general traffic evidence is slowdown-only, so this value is never negative.
effective_arrival_localYesAuthoritative arrival time in the destination's local time, or null when the local timezone is unavailable.
effective_duration_secondsYesAuthoritative duration for this response, in seconds, after any applicable traffic-based adjustment.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint, openWorldHint, and idempotentHint annotations, the description discloses meaningful behavioral details: live traffic is post-route enrichment that does not alter the path, truck traffic adjustments are slowdown-only, ETAs are ISO 8601 in the destination timezone, and the response echoes applied dimensions in costing_options.truck. These are non-obvious facts that materially affect how the agent interprets results.

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?

The description is a dense paragraph, but every sentence carries information essential to safe and correct use. It front-loads the core purpose, then layers important caveats (traffic behavior, presets, geometry formats) without repetition. It is longer than minimal, but the length is justified by the tool's 21-parameter complexity.

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 (21 parameters, 6 enums, output schema), the description is remarkably complete: it covers vehicle profiles, hazmat, tolls, traffic behavior, geometry selection with encoding details, elevation, waypoint limits (via maxItems), and units aliases. The output schema covers return structure, so the description adequately fills the knowledge gap for an agent to call this correctly.

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?

Though schema coverage is 100% and all parameters have descriptions, the tool description adds substantial semantic value: it explains that vehicle_profile presets set multiple dimensions in one parameter, gives concrete examples (DRY_VAN_53 = 4.11m tall, 36.3t, etc.), clarifies that individual truck_* parameters override a single field, and details the include_geometry options including auto-downgrade behavior and polyline6 decoding requirement. This goes well beyond the schema's per-field descriptions.

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 opens with 'Generate routes, ETAs, and turn-by-turn directions between locations,' which is a specific verb-resource statement that clearly distinguishes it from sibling tools like geocode, distance_matrix, and isochrone. It further differentiates by enumerating supported vehicle types and commercial routing presets.

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?

It provides explicit guidance for the truck use case ('Use vehicle_profile presets ... when routing trucks') and explains when to set hazmat, toll avoidance, and live traffic enrichment. It does not explicitly state when not to use this tool versus alternatives, but the context is clear enough that an agent can infer its primary role as the route generator.

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.

TDQS

A4.4/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose. Overlapping tools (geocode vs geocode_structured, explore vs search_places, map_match vs trace_attributes) are explicitly differentiated in their descriptions, with cross-references guiding correct selection. No two tools appear to do the same thing.

Naming Consistency4/5

Most tools follow a predictable verb_noun pattern (geocode, reverse_geocode, batch_geocode, search_places, resolve_intersection), but there are minor deviations: some tools use noun-only names (directions, traffic, weather) and a couple use noun_verb order (place_get, geofence_contains). This creates slight inconsistency but remains readable.

Tool Count4/5

At 19 tools, the set is slightly heavy but each tool earns its place by covering a distinct geospatial function. The breadth spans geocoding, routing, places, telematics, geofencing, traffic, weather, and account management, making the count reasonable for a comprehensive geo API.

Completeness5/5

The tool surface is remarkably complete for a geospatial server: forward, reverse, batch, structured, and intersection geocoding; routing, matrix, and isochrones; place search, exploration, and ID lookup; map matching, trace attributes, and point snapping; plus geofencing, traffic, weather, and quota management. No critical gaps or dead ends apparent.

Resources