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

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

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. Changed1 schema field changed
    • changedOutput schema / $defs / ElevationSample / properties / elevation_m / description
      Previous value: -"Elevation in metres, or `null` when the engine has no DEM tile\ncoverage at this point — Valhalla's own honest value, never a\nguess."New value: +"Elevation in metres, or `null` when the engine has no DEM tile\ncoverage at this point, Valhalla's own honest value, never a\nguess."
  2. 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"
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral burden and does so well: it discloses ordering of results, that elevation_m is null rather than guessed where DEM coverage is absent, and that the polyline form returns resampled lat/lon plus cumulative range_km. It omits auth/rate-limit or failure-mode info, keeping it short of a 5.

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?

Three dense sentences, front-loaded with the core action, then mode selection, then return semantics. No filler or redundancy with the title.

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 3-param read tool with an output schema and full schema coverage, the description supplies the one genuinely agent-relevant behavior not captured elsewhere: how missing coverage is represented (null, never a guess) and result ordering. Nothing needed to call it correctly is missing.

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% and the schema already states the mutual exclusivity and that resampling is ignored for points. The description reinforces this ('a bare list of coordinates') but adds little semantic detail beyond the structured fields, so the baseline of 3 applies.

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?

Opens with a specific verb+resource ('Sample terrain elevation') and immediately names the two distinct sampling modes it supports. An agent can distinguish it from route/weather siblings without opening the 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?

Explicitly states the mutually exclusive usage condition ('Provide points ... or encoded_polyline ... not both') and what resample_distance_m applies to. It does not name alternative tools for related needs, but within this tool the when-to-use guidance is unambiguous.

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