GeoSpark

Convert height (geoid models)

convert_height

Read-onlyIdempotent

Convert a height between the ellipsoid (GNSS, drones) and a national height datum with the official geoid model: AHD (AUSGeoid2020), ODN (OSGM15), NZVD2016 (NZGeoid2016), NAVD88 (GEOID18), or global EGM2008. Never estimate a geoid separation from memory: it is often tens of metres and varies by metres across a region.

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>",
      "height_m": "<height_m>",
      "from_reference": "<from_reference>",
      "to_reference": "<to_reference>"
    },
    "name": "convert_height"
  }
}

Input Schema

Name	Required	Description
`height_m`	Yes	The height to convert, in metres
`latitude`	Yes	Latitude in degrees (WGS84)
`longitude`	Yes	Longitude in degrees (WGS84)
`to_reference`	Yes	'ellipsoidal', AHD, ODN, NZVD2016, NAVD88 or EGM2008
`from_reference`	Yes	'ellipsoidal', AHD, ODN, NZVD2016, NAVD88 or EGM2008

Output Schema

Name	Required	Description	Default
`grids`	No
`units`	No	Unit of each numeric field
`method`	Yes
`status`	No		ok
`height_m`	Yes
`warnings`	No	Caveats to tell the user
`accuracy_m`	Yes
`provenance`	No	Source, licence, attribution, retrieval time and method
`geoid_model`	Yes
`separation_m`	Yes	Ellipsoidal height minus the datum height at this point
`to_reference`	Yes
`from_reference`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/safe, so the lower bar applies; the description still adds real value by explaining why the computation cannot be approximated (separation is often tens of metres and varies by metres across a region). It doesn't disclose behavior for coordinates outside a datum's coverage area or whether the conversion is symmetric.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action and the supported datums, then the warning that prevents the most likely agent error. No filler.

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?

Output schema exists, so return values need not be described, and all five parameters are documented. What is missing is edge-case behavior: what happens when the point lies outside a regional model's valid area, which is a realistic failure mode for this tool.

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. The description reinforces which reference strings are valid and implicitly justifies why latitude/longitude are required (geoid separation varies spatially), but adds no syntax, units, or default guidance beyond 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?

States a specific verb and resource ('Convert a height between the ellipsoid ... and a national height datum') and enumerates exactly which datums are supported (AHD/AUSGeoid2020, ODN/OSGM15, NZVD2016, NAVD88, EGM2008). This lets an agent distinguish it from 2D/projection siblings like transform_coordinates and from elevation lookup tools like get_elevation.

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 a clear directive on when to reach for it rather than improvising: 'Never estimate a geoid separation from memory.' Usage context (GNSS, drones) is named. It stops short of naming an alternative sibling or stating exclusion conditions (e.g., out-of-region coordinates), so it is clear but not fully routing.

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

All GeoSpark tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.