Skip to main content
Glama

elevation-mcp-server

Get Elevation Grid

elevation_get_grid
Read-onlyIdempotent

Sample a regular grid of terrain elevations across a bounding box and report the highest and lowest sampled points, the mean elevation, and the relief, plus the full elevation matrix with each cell's dataset. Values are point samples at grid nodes (box edges included), not cell averages, so a summit between nodes is missed; to refine a candidate high or low point, call again with a smaller box around it. Over open water, Mapzen cells are sea-floor depths. Rows times columns may not exceed 250.

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": {
      "south": "<south>",
      "west": "<west>",
      "north": "<north>",
      "east": "<east>"
    },
    "name": "elevation_get_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
colsNoGrid columns, west to east, edges included (2–25, default 10). rows × cols must be at most 250.
eastYesEastern edge longitude, decimal degrees.
rowsNoGrid rows, north to south, edges included (2–25, default 10). rows × cols must be at most 250.
westYesWestern edge longitude, decimal degrees. Must be less than east; a box crossing longitude 180 must be split into two calls.
northYesNorthern edge latitude, decimal degrees. Must be greater than south.
southYesSouthern edge latitude, decimal degrees.
sourceNoElevation source: auto (default) uses USGS 3DEP where it has data and Open Topo Data (SRTM, with Mapzen terrain tiles where SRTM has no data) for the rest; usgs_3dep uses 3DEP only; opentopodata uses Open Topo Data only. Case is ignored and spaces or hyphens read as underscores, so USGS-3DEP and open topo data are accepted; 3dep, usgs, and epqs are also aliases for usgs_3dep.auto

Output Schema

NameRequiredDescriptionDefault
colsNoNode columns applied.
eastNoEastern edge longitude, as requested.
rowsNoNode rows applied.
westNoWestern edge longitude, as requested.
errorNoPresent when the call failed. Absent on success.
northNoNorthern edge latitude, as requested.
southNoSouthern edge latitude, as requested.
noticeNoGuidance on nodes without data, boxes spanning the USGS 3DEP coverage edge, Mapzen sea-floor values, and node spacing against the source resolution.
summaryNoStatistics over the nodes with data.
attributionNoSources to credit for the returned values, one line per dataset that answered.
source_modeNoThe source the call used (auto unless the caller chose one).
elevations_mNoElevation matrix indexed [row][col], rows north to south, columns west to east.
cell_datasetsNoProvenance matrix with the same [row][col] indexing as elevations_m.
col_spacing_mNoEast-west distance between node columns at the box's center latitude, meters.
datasets_usedNoNumber of values each dataset answered.
latitudes_degNoLatitude of each row, north to south; row 0 is the north edge.
missing_cellsNoNodes no queried dataset answered.
row_spacing_mNoNorth-south distance between node rows, meters.
longitudes_degNoLongitude of each column, west to east; column 0 is the west edge.
cells_with_dataNoNodes with an elevation.
resolution_m_rangeNoRange of source resolutions over values that report one; absent when none does (all Mapzen).
vertical_referenceNoHeight-reference context per answering dataset, including unverified references and whether heights share a datum. No vertical datum conversion is performed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_bbox`: south is not below north, or west is not below east. `too_many_cells`: rows × cols exceeds 250. `no_coverage`: No grid node returned an elevation. `usgs_unavailable`: USGS 3DEP failed: a server error, rate limit, network error, or timeout that outlasted the retries (retryable), or a client error or unexpected status that retrying cannot fix (not retryable). `opentopodata_unavailable`: Open Topo Data failed: a server error, network error, timeout, or unreadable response that outlasted the retries (retryable), or an unexpected status that retrying cannot fix (not retryable). `opentopodata_rate_limited`: Open Topo Data kept answering HTTP 429 through the retries, or asked for a wait over 8 s. `opentopodata_daily_limit`: Only on the public Open Topo Data instance: this server has sent it 1,000 requests in the trailing 24 hours, so no request was sent. `opentopodata_config_rejected`: The Open Topo Data instance answered 401, 403, or 404, a redirect from a self-hosted instance, a 400 naming a dataset it lacks or a location limit below 100, or a 200 naming a dataset this server did not request. `sampling_deadline_exceeded`: The call's 45 s sampling budget ran out (a retry deadline, or a wait in either provider's request queue), or the USGS 3DEP lookups other calls had queued, plus this call's, would not drain within the calls' budgets, so it sent none and data.retryAfter gives the seconds until the queued lookups drain. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_bbox`: south is not below north, or west is not below east. `too_many_cells`: rows × cols exceeds 250. `no_coverage`: No grid node returned an elevation. `usgs_unavailable`: USGS 3DEP failed: a server error, rate limit, network error, or timeout that outlasted the retries (retryable), or a client error or unexpected status that retrying cannot fix (not retryable). `opentopodata_unavailable`: Open Topo Data failed: a server error, network error, timeout, or unreadable response that outlasted the retries (retryable), or an unexpected status that retrying cannot fix (not retryable). `opentopodata_rate_limited`: Open Topo Data kept answering HTTP 429 through the retries, or asked for a wait over 8 s. `opentopodata_daily_limit`: Only on the public Open Topo Data instance: this server has sent it 1,000 requests in the trailing 24 hours, so no request was sent. `opentopodata_config_rejected`: The Open Topo Data instance answered 401, 403, or 404, a redirect from a self-hosted instance, a 400 naming a dataset it lacks or a location limit below 100, or a 200 naming a dataset this server did not request. `sampling_deadline_exceeded`: The call's 45 s sampling budget ran out, or its individual USGS 3DEP lookups could not fit within the remaining budget alongside queued lookups. When data.retryAfter is present, it gives the seconds until the queued lookups drain. Other values are possible when a failure originates below the handler."
  2. Changed2 schema fields changed
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "not": {
      -      "required": [
      -        "error"
      -      ]
      -    },
      -    "required": [
      -      "south",
      -      "west",
      -      "north",
      -      "east",
      -      "rows",
      -      "cols",
      -      "latitudes_deg",
      -      "longitudes_deg",
      -      "row_spacing_m",
      -      "col_spacing_m",
      -      "elevations_m",
      -      "cell_datasets",
      -      "summary",
      -      "cells_with_data",
      -      "missing_cells",
      -      "datasets_used",
      -      "source_mode",
      -      "attribution"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "error"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "south",
      +      "west",
      +      "north",
      +      "east",
      +      "rows",
      +      "cols",
      +      "latitudes_deg",
      +      "longitudes_deg",
      +      "row_spacing_m",
      +      "col_spacing_m",
      +      "elevations_m",
      +      "cell_datasets",
      +      "summary",
      +      "cells_with_data",
      +      "missing_cells",
      +      "datasets_used",
      +      "source_mode",
      +      "vertical_reference",
      +      "attribution"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / vertical_reference
      Added value: +{
      +  "description": "Height-reference context per answering dataset, including unverified references and whether heights share a datum. No vertical datum conversion is performed.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only/idempotent/open-world annotations, the description discloses the sampling semantics that matter: values are point samples at grid nodes rather than cell averages, so a summit between nodes is missed. It also warns that Mapzen cells over open water are sea-floor depths and restates the 250-cell cap, which is genuine behavioral context for interpreting results.

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 front-loaded with the sampling action and the returned statistics, then adds limitations and the refinement tip in a logical order. It is slightly redundant in restating the 250-cell cap already present in the schema, but otherwise every sentence earns its place.

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?

An output schema exists, so return shape need not be fully explained, yet the description still summarizes the headline statistics and matrix. For a seven-parameter spatial sampler, it covers the key caveats (node sampling, water depths, cell cap, refinement strategy) that an agent needs to call and interpret it correctly.

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 rows, cols, bounds, and source are already fully documented, including the 250-cell cap and edge inclusion. The description adds no parameter meaning beyond the schema and only repeats 'box edges included' and the row/column limit.

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 uses a specific verb ('Sample') and resource ('a regular grid of terrain elevations across a bounding box') and states the outputs (high/low, mean, relief, full matrix with per-cell dataset). That is enough to separate it from point, profile, and line-of-sight siblings without opening another schema.

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 concrete operational guidance: refine a candidate high or low by calling again with a smaller box. It does not explicitly say when to prefer elevation_get_points or elevation_get_profile, but the grid-sampling scope is clear enough to imply the boundary.

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.