Skip to main content
Glama

Opentopodata

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Elevation

elevation
Read-onlyIdempotent

Elevation at points. Up to 100 locations per request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNojson (default) | geojson
datasetNoDefault "srtm90m".
samplesNoOptional: interpolate N samples between first and last point.
locationsYesArray of {lat, lon} (up to 100). Single object also accepted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetNoName of the DEM dataset used
resultsNoArray of elevation results for each location

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "locations": [
+      {
+        "lat": 40.7128,
+        "lon": -74.006
+      },
+      {
+        "lat": 34.0522,
+        "lon": -118.2437
+      }
+    ]
+  },
+  {
+    "dataset": "srtm90m",
+    "format": "geojson",
+    "locations": {
+      "lat": 51.5074,
+      "lon": -0.1278
+    },
+    "samples": 10
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "dataset": {
+      "description": "Name of the DEM dataset used",
+      "type": "string"
+    },
+    "results": {
+      "description": "Array of elevation results for each location",
+      "items": {
+        "properties": {
+          "elevation": {
+            "description": "Elevation in meters",
+            "type": "number"
+          },
+          "latitude": {
+            "description": "Latitude of the location",
+            "type": "number"
+          },
+          "longitude": {
+            "description": "Longitude of the location",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the read-only nature. The description adds the 'Up to 100 locations per request' limit, which is a valuable rate constraint beyond what annotations provide. No contradiction detected.

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 one compact sentence of eight words: 'Elevation at points. Up to 100 locations per request.' It is front-loaded, directly conveys the core function and key limit, and contains zero fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with only one required parameter, an output schema is present, and the input schema is fully described. The description provides the essential usage context and the batch limit. Nothing critical is missing given the richness of structured data, though it is understandably brief.

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%, with each parameter (format, dataset, samples, locations) already described in the input schema, including defaults and accepted shapes. The description adds no additional parameter-specific meaning, so the schema carries the full burden and baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool returns elevation at points and caps at 100 locations, making its function immediately clear. It lacks an explicit verb like 'get' but is unambiguous and no sibling tool overlaps, so no differentiation is needed.

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?

The description gives clear context: used for elevation lookup at specified points, with a 100-location upper bound implying batch use. There are no alternative tools with similar purpose in the sibling list, so exclusions aren't necessary. The limit helps the agent decide when this tool fits.

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

All Opentopodata toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources