Skip to main content
Glama

Get an elevation profile along a line

get_elevation_profile
Read-only

Compute a terrain elevation profile along a line of WGS84 points, such as a hike, and return distance/elevation pairs with total ascent and descent.

Instructions

Compute a terrain elevation profile along a line of WGS84 points (e.g. a hike). Returns distance/elevation pairs plus total ascent and descent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "points": "<points>"
    },
    "name": "get_elevation_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYesLine as ordered WGS84 points, at least 2
samplesNoNumber of profile samples

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, open-world operation. The description adds useful behavioral context by saying what is returned: distance/elevation pairs plus total ascent and descent. It does not mention rate limits, data-source caveats, or behavior for invalid lines, so it is not fully exhaustive.

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 definition is two compact sentences with the core purpose front-loaded. Every clause earns its place by stating the computation, input format, example use, and return shape.

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?

For a simple two-parameter read-only computation, the description covers purpose, input interpretation, and return contents. It lacks an explicit sibling comparison to get_elevation, which is the main remaining gap. The presence of complete schema descriptions offsets most other omissions.

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 both the points array and the samples parameter are already documented in structured form. The description reinforces that points are WGS84 and ordered but adds no detail about samples or sampling behavior. Baseline 3 is appropriate here.

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 uses a specific verb and resource: 'Compute a terrain elevation profile along a line of WGS84 points'. It also gives a concrete example ('e.g. a hike') that makes the scope clear. It does not explicitly distinguish itself from the sibling get_elevation, so it falls short of a 5.

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 hike example implies when this tool is appropriate, namely profiling along a route rather than querying a single point. However, it never states when not to use it or points to get_elevation for single-point elevation queries. Usage is therefore implied rather than explicit.

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

Deploy Server

Other Tools