gisgp

get_elevation

GISGP Lite (a 24-hour pass, a 7-day pass or a monthly plan) — pass the api_key of that account (or Authorization: Bearer). height above mean sea level of one point from Copernicus GLO-30 (30 m), read from the public elevation model (GLO-90 fallback). Returns JSON {ok, elevation_m, source, resolution_m, credit}; elevation_m is null at sea. For a free, coarser answer use get_terrain_profile.

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

Input Schema

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

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 18, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the authentication model (api_key of a paid account or Authorization: Bearer), the data source and its fallback resolution, and the null-at-sea edge case. It omits rate limits, error/failure behavior, and whether the model lookup is cached or live.

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

Conciseness3/5

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

Dense and mostly waste-free, but not front-loaded: the sentence opens with plan tiers and API-key billing before saying what the tool actually computes, so the purpose is buried behind commercial detail the agent needs only at call time.

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?

An output schema exists, so the description need not spell out return values, yet it still summarizes the payload and the sea-level null case — helpful and not redundant. Auth, source, and fallback are covered; the only substantive hole is coordinate semantics and error behavior.

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 0% for three parameters, and the description only explains api_key (account pass vs. Bearer token). lat/lon get no semantics at all — no CRS (presumably WGS84), no coordinate-order guidance, no valid ranges — which is a meaningful gap for a geospatial tool with an undocumented 2-required-param 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 operation on a specific resource: the height above mean sea level of ONE point, sourced from Copernicus GLO-30 with GLO-90 fallback. The word 'one point' implicitly distinguishes it from the profile siblings, and the named data source makes the tool's scope concrete.

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?

Explicitly routes the agent to an alternative with a condition: 'For a free, coarser answer use get_terrain_profile.' That is a real when-to-use-else signal. However, it never mentions get_elevation_profile, the closest sibling (line/transect elevation), so an agent choosing between point and profile sampling still has to infer the difference.

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

All gisgp tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.