Skip to main content
Glama

MapMap

by ai.mapmap
OverviewDiscussionsAdmin

elevation

Sample terrain elevation. Provide points (a bare list of coordinates) for point elevation, or encoded_polyline (optionally with resample_distance_m) for an along-route profile — not both. Returns one sample per point/resampled point in order; elevation_m is null wherever the engine's DEM tile set has no coverage at that point (never a guess). The encoded_polyline form also returns each sample's resampled lat/lon and cumulative range_km from the start.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pointsNoPoints to sample. Provide this or `encoded_polyline`, not both.
encoded_polylineNoA route as a Google encoded polyline with six digits of precision. Provide this or `points`, not both.
resample_distance_mNoResamples `encoded_polyline` at this spacing in metres before sampling height (ignored for `points`).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
samplesYesOne sample per input point (or per resampled shape point, in the `encoded_polyline` form), in order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / $defs / LatLon / anyOf
      Added value: +[
+  {
+    "properties": {
+      "lat": {
+        "description": "Latitude in decimal degrees (−90 to 90).",
+        "format": "double",
+        "type": "number"
+      },
+      "lon": {
+        "description": "Longitude in decimal degrees (−180 to 180).",
+        "format": "double",
+        "type": "number"
+      }
+    },
+    "required": [
+      "lat",
+      "lon"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "GeoJSON position [lon, lat]: longitude FIRST.",
+    "items": {
+      "format": "double",
+      "type": "number"
+    },
+    "maxItems": 2,
+    "minItems": 2,
+    "type": "array"
+  }
+]
    • changedInput schema / $defs / LatLon / description
      Previous value: -"A WGS84 coordinate pair in decimal degrees."New value: +"A WGS84 coordinate in decimal degrees: a {lat, lon} object (preferred), or a GeoJSON [lon, lat] array with LONGITUDE FIRST, the same order as every polygon field on this server."
    • removedInput schema / $defs / LatLon / properties
      Removed value: -{
-  "lat": {
-    "description": "Latitude in decimal degrees (−90 to 90).",
-    "format": "double",
-    "type": "number"
-  },
-  "lon": {
-    "description": "Longitude in decimal degrees (−180 to 180).",
-    "format": "double",
-    "type": "number"
-  }
-}
    • removedInput schema / $defs / LatLon / required
      Removed value: -[
-  "lat",
-  "lon"
-]
    • removedInput schema / $defs / LatLon / type
      Removed value: -"object"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does this thoroughly: it states that elevation_m is null where DEM coverage is missing and 'never a guess', and it discloses that the encoded_polyline form returns resampled lat/lon and cumulative range_km. This goes well beyond a basic 'returns elevation' statement and gives the agent confidence about edge cases.

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

Conciseness5/5

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

The description is compact and front-loaded: the core purpose is in the first sentence, and the key constraint ('not both') appears early. Every sentence earns its place, covering purpose, input modes, return behavior, and edge cases without redundancy. It is appropriately sized for a tool with three parameters and a rich output schema.

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 tool's moderate complexity (two mutually exclusive input modes, optional resampling, null-coverage behavior) and the presence of a rich output schema, the description covers everything an agent needs to invoke it correctly. It explains the trade-off between the two modes, the resampling parameter's scope, and the null semantics. The output schema handles return-value details, so the description doesn't need to repeat them.

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 baseline is 3. The description adds meaningful semantics beyond the schema: it explains the mutual exclusivity of points and encoded_polyline, clarifies that resample_distance_m is ignored for points, and describes the return behavior (one sample per point, null for missing coverage). It doesn't add much about the LatLon format, but the schema already covers that thoroughly. The extra behavioral context justifies a 4.

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 opens with a specific verb and resource ('Sample terrain elevation') and immediately distinguishes the two input modes (points vs encoded_polyline). It clearly states what the tool does and how it differs from the many sibling tools, which are mostly routing/geospatial operations rather than elevation sampling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'not both' for the two mutually exclusive input modes, and explains when to use each: point elevation vs along-route profile. It also clarifies that resample_distance_m applies only to encoded_polyline and is ignored for points. This is direct, actionable guidance with no ambiguity.

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

All MapMap toolsInspect
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.

Resources