hk-spatial-mcp

elevation_at

Get ground elevation in metres for any longitude/latitude coordinate to assess hiking relief, trail comfort, or slope warnings without an API key.

Instructions

Ground elevation in metres at a coordinate, from Esri's public Terrain3D service — no key. Handy for hiking/relief context (e.g. trail comfort, slope warnings) alongside CSDI layers.

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": {
      "lon": "<lon>",
      "lat": "<lat>"
    },
    "name": "elevation_at"
  }
}

Input Schema

Name	Required	Description	Default
`lat`	Yes
`lon`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.12.0Oct 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that no key is required and the return units, but omits accuracy, coordinate system expectations, coverage limits, and error behavior. Some value, but incomplete for a geospatial lookup.

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?

Two sentences, front-loaded with purpose. The second sentence adds useful context without bloat, though it could be slightly tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values needn't be explained, and the description mentions units and no-key access. However, gaps in coordinate format and accuracy/coverage limit completeness for a geospatial tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only says 'at a coordinate' without specifying lat/lon format, order, projection, or valid ranges. Minimal compensation for the missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (ground elevation at a coordinate), units (metres), and source (Esri Terrain3D). It does not explicitly differentiate from siblings, but the operation is unique among them.

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?

Provides clear usage context: handy for hiking/relief context, trail comfort, slope warnings, alongside CSDI layers. No explicit when-not or alternatives are given, but the use case is unambiguous.

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

Deploy Server