Skip to main content
Glama

HERE route (car/truck/bike/pedestrian, HGV profile)

here_route
Read-only

Calculate HGV-aware routes honoring height, width, weight, and axle limits, with traffic-aware timing, multiple transport modes, and UK toll data.

Instructions

Calculate a route with HERE Routing v8. Supports transportMode car | truck | pedestrian | bicycle | scooter. HGV routing: set transportMode="truck" and pass "truck" — e.g. {"heightM":4.2,"widthM":2.55,"lengthM":16.5,"grossWeightKg":44000,"weightPerAxleKg":11500,"axleCount":6,"trailerCount":1} — to honour height/width/weight/axle/hazmat/tunnel restrictions. Dimensions are metres and weights kg; they are converted to HERE vehicle[height] centimetres etc. Origin/destination/via accept either "lat,lng" or a free-text address (auto-geocoded, UK focus). departureTime or arrivalTime (RFC 3339 WITH offset, e.g. "2026-11-03T08:30:00+00:00") makes the route traffic-aware; without it the route is traffic-free (baseDuration == duration). By default returns a compact summary only (distance, duration, traffic delay, legs, critical notices). Opt in to polyline, turn-by-turn instructions, spans and tolls with the include* flags — polylines are large. UK defaults: units=metric, lang=en-GB, currency=GBP.

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": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "here_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
viaNoUp to 10 intermediate waypoints ("lat,lng" or addresses), visited in order.
langNoBCP-47 instruction language, default en-GB.
avoidNoRoad/area avoidance options.
truckNoHGV profile. Only used when transportMode is "truck".
unitsNoInstruction units (default metric).metric
originYesStart point: "lat,lng" (e.g. "53.4808,-2.2426") or an address (auto-geocoded, UK focus).
trafficNoUse live/typical traffic (default true). Set false for a traffic-free baseline.
currencyNoISO 4217 currency for toll costs, default GBP.
spansMaxNoMaximum spans to return when includeSpans=true (default 200).
billingTagNoOptional HERE billing tag for cost allocation.
arrivalTimeNoDesired arrival time, RFC 3339 with offset. Cannot be combined with departureTime.
destinationYesEnd point: "lat,lng" or an address.
routingModeNoOptimise for fastest (default) or shortest route.fast
alternativesNoNumber of alternative routes to return in addition to the best one (0-6).
emissionTypeNoToll emission class (sent as tolls[emissionType]). Only meaningful together with includeTolls=true.
includeSpansNoInclude route spans (speed limits, road names, functional class).
includeTollsNoInclude toll costs for this route (UK HGV Levy, M6 Toll, etc.).
departureTimeNoDeparture time, RFC 3339 with offset, e.g. "2026-11-03T08:30:00+00:00". Makes the route traffic-aware. Cannot be combined with arrivalTime.
transportModeNoTravel mode (default car). Use "truck" for HGV routing with the truck profile.car
includePolylineNoInclude the HERE Flexible Polyline per leg (encoded). Large — opt in.
returnAttributesNoAdvanced: extra HERE "return" attributes to request verbatim (e.g. ["routeLabels","typicalDuration"]).
includeTurnByTurnNoInclude HERE turn-by-turn action objects (advanced).
includeInstructionsNoInclude manoeuvre actions/instructions with offsets.
includePolylinePointsNoAlso decode the polyline into [lat,lng] points (requires includePolyline).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: traffic-aware versus traffic-free routing, default compact summaries, large polyline warnings, UK defaults, unit conversion for truck dimensions, and auto-geocoding behavior. These details help the agent anticipate results without contradicting readOnlyHint or openWorldHint.

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 front-loaded and every major sentence adds practical routing context. It is dense and somewhat long, but the length is justified by the tool's 24 parameters and nested truck profile.

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?

For a complex routing tool with nested objects and no output schema, the description covers the essential operational context: modes, HGV constraints, traffic timing, default output scope, opt-in flags, and regional defaults. An agent has enough information to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents parameters thoroughly. The description still adds useful cross-parameter meaning, especially the truck-profile example, unit conversion, and the requirement that includePolylinePoints depends on includePolyline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: "Calculate a route with HERE Routing v8." It clearly covers transport modes and HGV routing, but it does not explicitly distinguish this tool from siblings such as here_route_matrix or here_route_tolls.

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 gives clear usage conditions: set transportMode to "truck" for HGV routing, use departureTime or arrivalTime for traffic-aware routing, and opt in to extra output only when needed. It does not explicitly say when to choose a sibling tool instead.

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