Openrouteservice

Elevation Point

elevation_point

Read-onlyIdempotent

"Elevation / altitude at [coordinates]" / "how high is [location]" / "height above sea level for [lat,lng]" — elevation (meters above sea level) at a single point. Use for "what's the elevation of Denver", terrain queries, or attaching altitude to GPS records.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`geometry`	Yes	Per format_in (point: [lon, lat])
`format_in`	Yes	point \| geojson

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "format_in": "point",
+    "geometry": [
+      8.681495,
+      49.41461
+    ]
+  },
+  {
+    "format_in": "geojson",
+    "geometry": {
+      "coordinates": [
+        2.352222,
+        48.856613
+      ],
+      "type": "Point"
+    }
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Elevation at point response from OpenRouteService",
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds value by specifying the output unit ('meters above sea level') and the single-point constraint. No contradictions with annotations.

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 a single sentence with embedded examples and usage hints, fully front-loaded with the key terms. Every word is purposeful and contributes to clarity.

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 simplicity (2 parameters, straightforward purpose) and the presence of an output schema, the description is complete. It covers the main use case and parameter details sufficiently.

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 coverage is 100%, so baseline 3 applies. The description provides example geometries and explains the 'format_in' values, but these details are also in the schema. No significant extra meaning beyond the schema.

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 the tool returns elevation/altitude at a single point, provides example queries ('how high is [location]'), and distinguishes from the sibling tool 'elevation_line' by specifying 'at a single point'.

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 explicitly mentions use cases like 'what's the elevation of Denver', terrain queries, and attaching altitude to GPS records. It does not explicitly state when not to use, but the context and sibling list imply alternatives like elevation_line for lines.

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

All Openrouteservice 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.