Skip to main content
Glama
Sign In

Open Elevation

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Elevations

get_elevations
Read-onlyIdempotent

Batch elevation lookup. Pass an array of {latitude, longitude} points (up to 1,000 per call recommended). Returns each with elevation in metres.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "locations": [
        {
          "latitude": 40.7128,
          "longitude": -74.006
        },
        {
          "latitude": 34.0522,
          "longitude": -118.2437
        },
        {
          "latitude": 41.8781,
          "longitude": -87.6298
        }
      ]
    },
    "name": "get_elevations"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationsYesArray of {latitude, longitude} objects

Output Schema

NameRequiredDescriptionDefault
countYesNumber of results returned
resultsYesArray 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": [
+      {
+        "latitude": 40.7128,
+        "longitude": -74.006
+      },
+      {
+        "latitude": 34.0522,
+        "longitude": -118.2437
+      },
+      {
+        "latitude": 41.8781,
+        "longitude": -87.6298
+      }
+    ]
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of results returned",
+      "type": "integer"
+    },
+    "results": {
+      "description": "Array of elevation results for each location",
+      "items": {
+        "properties": {
+          "elevation_m": {
+            "description": "Elevation in metres above mean sea level",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "latitude": {
+            "description": "Latitude of the location",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "longitude": {
+            "description": "Longitude of the location",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "results"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds that it returns elevation in meters and recommends a batch limit. This is moderate additional context but does not cover potential errors or coordinate validity.

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?

Two sentences, front-loaded with the core purpose. Every sentence adds value with no redundancy. Highly efficient.

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 has an output schema, the description need not detail return values beyond 'elevation in metres'. It covers input format, limit, and output sufficiently for a simple batch lookup tool.

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 baseline is 3. The description adds the recommended limit of 1,000 points, providing useful semantic context beyond the schema's property description.

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 clearly states 'Batch elevation lookup', specifying verb and resource. It distinguishes from sibling 'get_elevation' by implying batch processing. The input and output are explicitly described.

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

Usage Guidelines3/5

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

The description implies usage for multiple points with a recommended limit of 1,000, but does not provide explicit guidance on when to use the singular sibling 'get_elevation' or conditions for avoiding this tool.

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

All Open Elevation 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