here-hgv-mcp

HERE reverse geocode (coordinates → address)

here_reverse_geocode

Read-only

Convert WGS84 coordinates into the nearest address, street, or locality. Use it to name route origins/destinations or report incident and vehicle locations, with an optional radius for nearby matches.

Instructions

Convert WGS84 coordinates into the nearest address/street/locality using the HERE Reverse Geocoding v7 API. Useful for naming a route origin/destination or for reporting where an incident or vehicle is. radiusM limits the search around the point (HERE "circle" filter); omit it for the nearest match only. Returns formatted addresses with country/postcode/street/house number and the distance to the requested point.

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_reverse_geocode"
  }
}

Input Schema

Name	Required	Description
`lang`	No	BCP-47 language for addresses, default en-GB.
`limit`	No	Maximum addresses to return (default 1).
`types`	No	Restrict to result types, e.g. ["address","street"].
`radiusM`	No	Search radius in metres around the point (1-5000). Omit for the nearest result only.
`latitude`	Yes	WGS84 latitude in decimal degrees, e.g. 53.4808.
`longitude`	Yes	WGS84 longitude in decimal degrees, e.g. -2.2426.

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 already establish readOnlyHint=true and openWorldHint=true, and the description adds real value on top: radiusM is described as HERE's 'circle' filter with nearest-match semantics, and the return shape (formatted address components plus distance to the requested point) is disclosed. It does not cover failure behavior (e.g. no match found) or rate/limit constraints, which keeps it below 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?

Four sentences, all front-loaded with purpose first, then use cases, then the radius caveat, then return contents. It is dense and readable; the radiusM sentence mildly duplicates the schema, which is the only slack.

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 no output schema, the description correctly compensates by describing the returned address fields and distance. For a 6-parameter, read-only lookup tool the essentials are covered; only edge-case behavior (empty results, whether limit interacts with radiusM) is left unaddressed.

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 every parameter including radiusM, types, lang and limit is already documented in the schema. The description's radiusM sentence largely restates the schema's own 'omit for the nearest result only' wording, adding little semantic meaning beyond the structured fields. Baseline 3 applies.

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+resource: 'Convert WGS84 coordinates into the nearest address/street/locality', and names the underlying API (HERE Reverse Geocoding v7). The direction of conversion (coordinates → address) implicitly and clearly separates it from the forward-geocoding sibling here_geocode.

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 use cases ('naming a route origin/destination', 'reporting where an incident or vehicle is') and a conditional instruction for radiusM ('omit it for the nearest match only'). It stops short of explicit when-not guidance or naming a sibling alternative, so it is clear context rather than full 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