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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cols`	No	Grid columns, west to east, edges included (2–25, default 10). rows × cols must be at most 250.
`east`	Yes	Eastern edge longitude, decimal degrees.
`rows`	No	Grid rows, north to south, edges included (2–25, default 10). rows × cols must be at most 250.
`west`	Yes	Western edge longitude, decimal degrees. Must be less than east; a box crossing longitude 180 must be split into two calls.
`north`	Yes	Northern edge latitude, decimal degrees. Must be greater than south.
`south`	Yes	Southern edge latitude, decimal degrees.
`source`	No	Elevation 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

TableJSON Schema

Name	Required	Description
`cols`	No	Node columns applied.
`east`	No	Eastern edge longitude, as requested.
`rows`	No	Node rows applied.
`west`	No	Western edge longitude, as requested.
`error`	No	Present when the call failed. Absent on success.
`north`	No	Northern edge latitude, as requested.
`south`	No	Southern edge latitude, as requested.
`notice`	No	Guidance on nodes without data, boxes spanning the USGS 3DEP coverage edge, Mapzen sea-floor values, and node spacing against the source resolution.
`summary`	No	Statistics over the nodes with data.
`attribution`	No	Sources to credit for the returned values, one line per dataset that answered.
`source_mode`	No	The source the call used (auto unless the caller chose one).
`elevations_m`	No	Elevation matrix indexed [row][col], rows north to south, columns west to east.
`cell_datasets`	No	Provenance matrix with the same [row][col] indexing as elevations_m.
`col_spacing_m`	No	East-west distance between node columns at the box's center latitude, meters.
`datasets_used`	No	Number of values each dataset answered.
`latitudes_deg`	No	Latitude of each row, north to south; row 0 is the north edge.
`missing_cells`	No	Nodes no queried dataset answered.
`row_spacing_m`	No	North-south distance between node rows, meters.
`longitudes_deg`	No	Longitude of each column, west to east; column 0 is the west edge.
`cells_with_data`	No	Nodes with an elevation.
`resolution_m_range`	No	Range of source resolutions over values that report one; absent when none does (all Mapzen).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world behavior, yet the description adds substantive semantics: values are point samples at nodes (not cell averages) so an inter-node summit is missed, and over open water Mapzen cells are sea-floor depths. These caveats materially change interpretation of results; only auth/rate-limit behavior is absent.

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?

Front-loaded with what the tool returns, then the sampling caveat, the refinement tip, and the water/limit notes. Every sentence carries information, though the output enumeration is somewhat redundant given an output schema exists.

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?

With an output schema present, the description need not restate return values, yet it covers the sampling model, the water interpretation, the iterative refinement path, and the size cap. An agent has everything needed to call this correctly and interpret the result.

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 the schema already documents rows, cols, edges, source aliasing, and the 250-cell cap. The description largely repeats the rows×cols limit and source behavior already in the schema, adding little beyond the baseline.

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 verb (sample) and resource (regular grid of terrain elevations) with the scope (across a bounding box) and the outputs (high/low/mean/relief plus full matrix). This clearly distinguishes it from the point, profile, and line-of-sight siblings without needing to name them.

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?

Gives an explicit refinement workflow: 'to refine a candidate high or low point, call again with a smaller box around it.' It does not explicitly compare against the sibling tools (get_points, get_profile, check_line_of_sight), so the agent must infer when a grid is preferable to those, but the practical usage context is clear.

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

All elevation-mcp-server 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.