here-hgv-mcp

HERE isoline (reachable area by time or distance)

here_isoline

Read-only

Calculate reachable areas from a point within time or distance ranges, including HGV-aware truck routing that respects height, weight, hazmat and tunnel restrictions.

Instructions

Calculate the area reachable from a point within one or more time or distance ranges (isochrone/isodistance) using HERE Isoline Routing v8. HGV support: transportMode="truck" plus the same "truck" profile as here_route (metres/kg) so reachability respects height/weight/hazmat/tunnel restrictions. rangeType="time" (ranges in seconds, default [900,1800,2700] = 15/30/45 min) or "distance" (ranges in metres, default [5000,10000,15000]). Returns one polygon per range as HERE Flexible Polyline geometry; set includePolygonPoints=true to also get decoded [lat,lng] rings (larger). UK defaults: departure now with live traffic, en-GB notices, metric.

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>"
    },
    "name": "here_isoline"
  }
}

Input Schema

Name	Required	Description	Default
`avoid`	No	Road/area avoidance options.
`truck`	No	HGV profile. Only used when transportMode is "truck".
`origin`	Yes	Centre point: "lat,lng" or an address (auto-geocoded, UK focus).
`ranges`	No	1-7 ranges. Time: seconds, max 32400 (9 h). Distance: metres, max 1000000 (1000 km). Defaults: [900,1800,2700] s or [5000,10000,15000] m.
`traffic`	No	Consider live traffic (default true).
`rangeType`	No	Range unit: time (seconds) or distance (metres).	time
`arrivalTime`	No	Instead of departureTime: area from which the origin is reachable by this time.
`optimizeFor`	No	Isoline calculation optimisation (default balanced).	balanced
`departureTime`	No	Departure time (RFC 3339 WITH offset, e.g. "2026-11-03T08:30:00+00:00"). Omit to use "now" with live traffic.
`transportMode`	No	Travel mode (default car). Use "truck" for HGV reachability.	car
`includePolygonPoints`	No	Decode polygons to [lat,lng] rings in the response (default false; encoded geometry is always returned).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds real behavioral context: one polygon per range returned as Flexible Polyline, includePolygonPoints producing larger decoded rings, live-traffic-by-default departure behaviour, and en-GB/metric UK defaults. It stops short of noting cost, rate limits, or failure modes, but the added disclosure is substantial.

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?

A single dense but front-loaded paragraph: purpose first, then HGV support, then mode/units, then return shape, then regional defaults. Nothing is padding, though the default range arrays are partly repeated from the schema.

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 11-parameter tool with nested objects and no output schema, the description covers return shape, units, defaults, mode dependencies, and regional behaviour well. Minor gaps remain around limits/errors and the avoid sub-object, but those are documented in the schema.

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 a 3 is the floor, but the description adds meaning beyond the schema: the default range arrays (900/1800/2700 s, 5000/10000/15000 m), the unit semantics per rangeType, the dependency between transportMode and the truck object, and the size cost of includePolygonPoints.

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 — "Calculate the area reachable from a point within one or more time or distance ranges (isochrone/isodistance)" — and names the underlying API (HERE Isoline Routing v8). This is clearly distinguishable from point-to-point siblings like here_route or here_route_matrix.

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 concrete selection guidance between the two modes (rangeType="time" in seconds vs "distance" in metres) and states the HGV condition (transportMode="truck" plus the truck profile). It references here_route only for profile consistency, not as an explicit alternative to choose instead, so there is no stated when-not-to-use rule.

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

Deploy Server