GeoSpark

Elevation

get_elevation

Read-onlyIdempotent

Ground elevation in metres (Copernicus GLO-30, Open Elevation fallback), with its vertical datum and accuracy.

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": "get_elevation"
  }
}

Input Schema

Name	Required	Description	Default
`latitude`	Yes	Latitude in degrees (WGS84)
`longitude`	Yes	Longitude in degrees (WGS84)

Output Schema

Name	Required	Description	Default
`units`	No	Unit of each numeric field
`status`	No		ok
`quality`	No	e.g. vertical_accuracy_le90_m
`latitude`	Yes
`warnings`	No	Caveats to tell the user
`longitude`	Yes
`provenance`	No	Source, licence, attribution, retrieval time and method
`attribution`	No
`elevation_m`	Yes
`vertical_datum`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, so the burden is low. The description adds genuinely useful context beyond them: the primary source (Copernicus GLO-30), the Open Elevation fallback (signaling possible quality variance), and that the datum and accuracy come back with the value.

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?

A single front-loaded sentence that packs units, source stack, and return qualifiers with zero filler. Nothing can be removed without losing information.

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?

For a two-parameter point-query with a full output schema and complete annotations, the description covers what the value means and its provenance. The only gap is the absence of any statement about coverage or limitations (e.g., ocean/no-data points), which would matter for an open-world terrain 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 coverage is 100%, with both latitude and longitude documented as WGS84 degrees including min/max bounds in the schema. The description adds no further parameter semantics, so the baseline 3 applies.

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 resource (ground elevation) with units (metres), the data sources used, and what accompanies the value (vertical datum, accuracy). It is clearly distinct from the geocoding/routing siblings, though it never explicitly contrasts itself with a sibling like location_report that might also carry elevation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no alternatives are named. The agent must infer from the name and the lat/lon inputs alone that this is the single-point elevation lookup versus any composite tool.

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.