Openrouteservice

Elevation Line

elevation_line

Read-onlyIdempotent

"Elevation profile along a route" / "hiking trail elevation gain" / "topographic profile of [path]" / "how hilly is this route" — elevation samples along a geometry (linestring). Pass geojson / polyline / encodedpolyline5 / encodedpolyline6. Use for hiking elevation gain, cycling grade analysis, trail planning, terrain profiles.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`geometry`	Yes	Per format_in
`format_in`	Yes	geojson \| polyline \| encodedpolyline5 \| encodedpolyline6

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": "geojson",
+    "geometry": {
+      "coordinates": [
+        [
+          8.681495,
+          49.41461
+        ],
+        [
+          8.687872,
+          49.420318
+        ]
+      ],
+      "type": "LineString"
+    }
+  },
+  {
+    "format_in": "polyline",
+    "geometry": "u{~vFvyys@fS"
+  }
+]

changedOutput schema / (root)

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

First observedMay 20, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds input format details (geojson, polyline, etc.) and usage scenarios but does not elaborate beyond the annotations' safety profile.

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?

A single, well-structured sentence that front-loads the purpose with quoted synonyms, followed by a list of use cases. Every phrase adds value without redundancy.

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), annotations covering safety, and an existing output schema, the description provides all necessary context: purpose, input formats, and typical applications.

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 baseline is 3. The description adds value by explicitly listing supported geometry formats and indicating the geometry is a linestring, reinforcing the schema's format_in enum and geometry 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 the tool provides elevation samples along a linestring geometry using verbs like 'elevation profile', 'elevation gain', and 'topographic profile'. It distinguishes from the sibling 'elevation_point' by focusing on routes vs points.

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 lists use cases: hiking elevation gain, cycling grade analysis, trail planning, terrain profiles. It does not provide exclusions or direct comparisons, but the sibling 'elevation_point' implicitly covers when not to use this tool.

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.