here-hgv-mcp

HERE static map image (markers + route line)

here_map_image

Render static HERE maps centered on coordinates with optional markers and route lines, then save as PNG/JPEG and return the local file path for viewing or sharing.

Instructions

Render a static HERE map (Map Image API v3) centred on a point, with optional numbered/pinned markers and an optional route line, then save it as a PNG/JPEG and return the local file path. UK default style "explore.day". width/height default 800×600. zoom default 13 (city level); 9-10 gives a regional overview for a long HGV route. Route line: pass routePolyline (the encoded HERE Flexible Polyline returned by here_route includePolyline) — it is sent as HERE's compact overlay, so long routes do not overflow the URL — OR routePoints as [[lat,lng],…] (downsampled to 200 points). Markers are formatted as pinned labels. The saved file can be opened with an image viewer / read_image tool. The returned URL is credential-free; the HERE API key is never exposed (the image is fetched server-side and written to HERE_MAP_OUTPUT_DIR). For a simple “where is this?” image omit markers; for a delivery map pass markers for each stop.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "here_map_image"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Map label language (ISO 639-1 two letters only, default "en" derived from en-GB).
`zoom`	No	Zoom level 0-22 (default 13). Use 9-10 for a whole-UK/HGV route overview.
`hiRes`	No	Render at 2× scale for high-DPI displays (default false).
`style`	No	HERE map style (default explore.day; try "explore.night" or "satellite.day").	explore.day
`width`	No	Image width in pixels (64-2048, default 800).
`format`	No	Image format (default png8; use png24 for gradients or jpeg for photos).	png8
`height`	No	Image height in pixels (64-2048, default 600).
`markers`	No	Up to 20 markers to draw on the map.
`filename`	No	Optional output filename (extension corrected automatically).
`latitude`	Yes	Map centre latitude, e.g. 53.4808.
`longitude`	Yes	Map centre longitude, e.g. -2.2426.
`saveToFile`	No	Download and save the image locally (default true). Set false to only get the keyless URL.
`routePoints`	No	Route line as explicit [[lat,lng],…] points (alternative to routePolyline).
`routePolyline`	No	Encoded HERE Flexible Polyline to draw as a route line (e.g. from here_route includePolyline=true). Sent as a compact overlay, so long routes are safe.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: the image is fetched server-side, written to HERE_MAP_OUTPUT_DIR, and returned as a local file path plus a credential-free URL that never exposes the API key. It also explains that routePolyline is sent as a compact overlay so long routes do not overflow the URL, which is valuable operational context.

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 single dense paragraph that front-loads the core action and output before moving to defaults, route handling, and usage examples. It is generally efficient, but it repeats schema defaults such as 800×600 and zoom 13, which slightly dilutes conciseness.

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 14-parameter image-generation tool with no output schema, the description is complete enough: it explains the rendered output, file-saving behavior, output location, credential-free URL, route input alternatives, and marker usage. An agent has what it needs to invoke the tool correctly without additional return-value documentation.

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 description coverage is already 100%, so the baseline is 3, but the description adds meaning by explaining that routePoints are downsampled to 200 points and routePolyline uses HERE's compact overlay format. It also clarifies practical defaults for zoom and dimensions, though some of that repeats schema-level details.

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 states a specific verb and resource: render a static HERE map image centred on a point, optionally with markers and a route line, save it as PNG/JPEG, and return the local file path. It clearly distinguishes this from routing and geocoding siblings by focusing on image rendering and file output.

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 concrete usage patterns: omit markers for a simple 'where is this?' image, pass markers for a delivery map, and choose routePolyline versus routePoints depending on the route data source. It references here_route includePolyline as the source of encoded polylines, but does not explicitly state when to use here_route instead of this tool for route calculation.

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

Deploy Server