here-hgv-mcp

HERE waypoint sequence (multi-stop order optimisation)

here_waypoint_sequence

Read-only

Optimize the visiting order for a multi-stop HGV delivery run by providing a depot, optional end, and stops; returns the best sequence with leg distances, times, and totals.

Instructions

Find the optimal visiting order for a multi-drop run using HERE Waypoints Sequence v8 (findsequence2). Provide a start (depot), an optional end, and the stops to visit. The response lists the optimised order with per-leg distance/time and totals — ideal for planning a delivery round for an HGV. improveFor="time" (default) or "distance". transportMode="truck" with the "truck" profile applies HGV restrictions for the whole sequence (metres/kg converted to HERE cm/kg with units). departureTime is RFC 3339 with offset; it defaults to "now" because live traffic is factored into the sequence. avoidFeatures uses HERE's mode route-features: tollroad, motorway, boatFerry, railFerry, tunnel, dirtRoad (strict avoidance).

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": {
      "start": "<start>",
      "waypoints": "<waypoints>"
    },
    "name": "here_waypoint_sequence"
  }
}

Input Schema

Name	Required	Description	Default
`end`	No	Optional end location (e.g. return to depot).
`start`	Yes	Depot/start location: "lat,lng" or address (auto-geocoded).
`truck`	No	HGV profile. Only used when transportMode is "truck".
`waypoints`	Yes	Stops to visit, 1-50, in no particular order — HERE computes the optimal order.
`improveFor`	No	Optimise for total travel time (default) or distance.	time
`avoidFeatures`	No	Road features to strictly avoid for the whole sequence.
`departureTime`	No	Departure time (RFC 3339 with offset) or "now". Defaults to "now" so traffic is considered.
`transportMode`	No	Travel mode (default car). Use "truck" for HGV sequence.	car
`excludeCountries`	No	ISO 3166-1 alpha-3 countries to exclude from the sequence.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description adds the meaningful behavior: departureTime defaults to "now" because live traffic is factored into the sequence, avoidFeatures is strict avoidance for the whole sequence, truck restrictions apply to the entire sequence, and metres/kg are converted to HERE's cm/kg. It also sketches the response shape. It stops short of error/limit behavior or geocoding fallback details, so not a 5.

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?

Purpose is front-loaded in sentence one, usage and response shape follow, then parameter notes. It is dense and slightly run-on toward the end, but nearly every clause carries information an agent would otherwise have to infer.

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?

With 9 parameters, a nested truck object, and no output schema, the description does the right things: it summarizes the return value (optimised order with per-leg distance/time and totals) and explains the truck profile and traffic-driven departure default. Remaining gaps — address geocoding failures, the 50-stop ceiling, error behavior — are minor and partly covered by the schema.

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 the baseline is 3 and the schema already carries most parameter meaning. The description adds cross-parameter context — transportMode="truck" with the "truck" profile applies HGV restrictions for the whole sequence, and improveFor defaults to time — but restates several details (units, strict avoidance) already present in the schema.

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?

Opens with a specific verb and resource: "Find the optimal visiting order for a multi-drop run using HERE Waypoints Sequence v8 (findsequence2)". That is unmistakably different from a plain point-to-point route or matrix call, and it names the underlying HERE service, so an agent can separate it from here_route/here_route_matrix without opening a schema.

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 situational context: "ideal for planning a delivery round for an HGV", plus the required input shape (start, optional end, stops). It does not name alternatives or state when NOT to use it (e.g. single A-to-B routing belongs to here_route), so it falls short of explicit routing guidance.

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

Deploy Server