Skip to main content
Glama
Sign In
here-hgv-mcp

here-hgv-mcp

by craigst
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

HERE geocode (address → coordinates)

here_geocode
Read-only

Convert free-text addresses or place names into WGS84 coordinates for routing, search, or mapping, returning ranked matches with optional country focus.

Instructions

Resolve a free-text address or place to WGS84 coordinates using the HERE Geocoding & Search v7 API. Use this first when you only have an address and need a point for routing, search or mapping. UK defaults: a country focus of GBR (set countryFocus to another ISO-3166-1 alpha-3 code, or "ANY" to search worldwide) and lang=en-GB. Examples: {"q":"10 Downing Street, London"}, {"q":"Trafford Park, Manchester"}, {"q":"M6 Toll","types":["place"]}. Returns a ranked list with formatted address components, lat/lng, bounding box and match score. Empty results are a success with count=0.

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": {
      "q": "<q>"
    },
    "name": "here_geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesFree-text query: full address, postcode, place or landmark, e.g. "10 Downing Street, London" or "Trafford Park".
atNoOptional context point "lat,lng" used to rank nearby matches (e.g. "53.4808,-2.2426").
bboxNoOptional bounding box filter [west, south, east, north] in degrees. Overrides countryFocus.
langNoBCP-47 language for returned names, default en-GB (e.g. "cy" for Welsh labels where available).
limitNoMaximum results to return (1-100, default 5).
typesNoRestrict result types, e.g. ["address","street"]. Omit for all types.
countryFocusNoISO 3166-1 alpha-3 country to filter results, e.g. GBR. Defaults to the server default (GBR). Use "ANY" to search all countries.
politicalViewNoOptional ISO 3166-1 alpha-3 political view, e.g. CYP for a CYPRUS-specific view.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already declaring the safety profile, the description still contributes meaningful behavior: UK-biased defaults (countryFocus GBR, lang en-GB), bbox overriding countryFocus, and that zero matches return success with count=0 rather than an error. Coverage gaps are minor – nothing on rate limits, auth, or pagination of large result sets.

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 and the usage directive are front-loaded, followed by defaults and examples, which is the right order for a scanning agent. The three example queries are slightly redundant against the schema's own examples, costing a little density but adding realistic invocation shapes.

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?

No output schema exists, so the description carries the return burden and does so – ranked list with formatted components, lat/lng, bbox and match score, plus the empty-result semantics. Missing only edge-case behavior (multiple matches ranking rationale, error cases for malformed queries).

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 defaults and examples is already documented in the schema. The description's parameter notes (countryFocus,

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 ('Resolve a free-text address or place to WGS84 coordinates using the HERE Geocoding & Search v7 API') and pins the direction address→coordinates, which implicitly separates it from the reverse-geocode sibling. An agent can tell instantly what it gets back and when it applies.

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?

'Use this first when you only have an address and need a point for routing, search or mapping' gives a clear selection context, and the bbox/overrides note prevents conflicting-filter mistakes. It stops short of naming here_reverse_geocode as the counterpart for coordinate→address, so the exclusion is inferred rather than explicit.

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

Deploy Server

Other Tools