gisgp

get_terrain_profile

Get the ground elevation (metres above sea level) at a coordinate — e.g. "what's the elevation here", "is this point in a flood-risk lowland", "elevation at this address". Via Open-Meteo (Copernicus DEM GLO-90, no key, free, ~90m resolution).

Returns JSON: {ok, lon, lat, elevation_m, source}.

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

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.

AddedJul 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description discloses the data source (Open-Meteo Copernicus DEM), no API key needed, free usage, ~90m resolution, and the return JSON structure. Lacks error handling or coordinate order details, but provides substantial context.

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?

Three sentences covering purpose, data source, and return format. The return format sentence is redundant given the output schema, but it is brief and adds emphasis. Overall efficient with no fluff.

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

Completeness5/5

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

For a simple 2-param read-only tool with an output schema, the description covers purpose, data source, resolution, no-key access, and return shape. Missing edge cases are not critical for selection and invocation.

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%, so the description must compensate. It refers to 'a coordinate' and output includes lon/lat, but does not explicitly state coordinate format (decimal degrees) or that addresses require prior geocoding. The example 'elevation at this address' could mislead an agent into passing an address string.

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?

Clearly states 'Get the ground elevation (metres above sea level) at a coordinate' with specific unit and resource. Examples like 'what's the elevation here' help distinguish it from sibling assessment tools that perform broader analyses.

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 example intents (flood-risk lowland, address elevation) that imply when to use. Does not explicitly contrast with sibling tools like assess_property_hazard, but the context is clear for a direct elevation lookup.

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.