Skip to main content
Glama

Point Elevation

get_point_elevation
Read-onlyIdempotent

Purpose: read one contextual elevation worldwide from Copernicus GLO-30 surface data, or an operator-configured Open Topo Data-compatible service. When to use: when a user asks about elevation at a known worldwide point. Returns: finite point elevation in metres, provider-declared dataset, nominal grid spacing, expected EGM96 vertical datum, retrieval time and explicit limitations. Limitations: Copernicus includes buildings and vegetation and uses EGM2008 heights. A configured service retains its own expected datum; no public test-service default or Mapbox RGB guessing. ASTER and SRTM have different latitude/void coverage. Provider deployment/version, local accuracy, licence and datum are unverified. One point does not establish slope, contours, drainage, flood risk, wind exposure, measured site levels or 3D terrain. Parameter guidance: supply country-aware address, resolved site_ref or coordinates {lat,lng} with explicit country_code. Non-UK address lookup also requires the configured geocoder. Missing, invalid or out-of-range source data returns an explicit error, never zero elevation or low risk. Chaining: every response returns site_ref; pass it unchanged into another Atlasly tool to reuse the canonical site, coordinates, boundary confidence, LPA, evidence links, and project context.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_point_elevation"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoSite address or postcode, with town and country outside the UK. Alternatively pass site_ref from an earlier result; do not send both for different locations.
site_refNoCanonical site_ref returned by any previous Atlasly tool. Pass it unchanged to chain the same resolved site into this call; address, search_area, or project_id will be filled from it when omitted.
coordinatesNoUser-supplied WGS84 point {lat, lng}. Send with country_code. The point is not reverse-geocoded, so its address and planning jurisdiction stay unverified.
country_codeNoISO two-letter country code such as gb, us, in or fr. Required with coordinates and for addresses outside the UK.

Output Schema

NameRequiredDescriptionDefault
queryNo
statusYes
detailsNo
messageNo
sourcesYes
headlineYes
site_refYes
retryableNo
error_codeNo
atlasly_linkYes
error_sourceNo
human_messageNo
key_data_pointsYes
top_constraintsYes
confidence_notesYes
executive_summaryYes
next_best_actionsYes
top_opportunitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Site address or postcode, with town and country outside the UK. Alternatively pass site_ref from an earlier result; do not send both for different locations."
    • addedInput schema / properties / coordinates / description
      Added value: +"User-supplied WGS84 point {lat, lng}. Send with country_code. The point is not reverse-geocoded, so its address and planning jurisdiction stay unverified."
    • addedInput schema / properties / country_code / description
      Added value: +"ISO two-letter country code such as gb, us, in or fr. Required with coordinates and for addresses outside the UK."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description adds substantial context beyond the annotations: source data, vertical datum expectations, provider caveats, explicit error behavior instead of zero elevation, and chaining behavior via site_ref. With readOnly, idempotent and openWorld annotations already present, these details make the tool's behavior and limitations unusually transparent.

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?

The description is well structured and front-loads purpose and usage before limitations and parameter guidance. It is somewhat long and repeats some return-value details that the output schema likely covers, but the length is largely justified by the tool's data-source and datum caveats.

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?

Given the complexity of geographic elevation data, multiple input modes, provider variance and datum limitations, the description is complete enough for correct invocation. It covers purpose, usage, source limitations, parameter handling, error semantics and chaining, while the output schema carries return-value structure.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents parameters well. The description adds useful combined guidance about using a country-aware address, a resolved site_ref, or coordinates with explicit country_code, and notes that non-UK address lookup requires a configured geocoder, which goes slightly beyond the raw 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?

The description states a specific verb and resource: read one contextual elevation worldwide from Copernicus GLO-30 or a configured Open Topo Data service. It clearly scopes the tool to point elevation, which distinguishes it from sibling tools such as get_flood_risk or analyze_site.

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?

It gives a clear when-to-use condition: when a user asks about elevation at a known worldwide point. It also lists important exclusions, such as slope, contours, drainage, flood risk, wind exposure and measured site levels, though it does not explicitly name alternative sibling tools for those needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources