Skip to main content
Glama

get_elevations

Read-onlyIdempotent

Compare GSI elevations for 1 to 10 WGS84 points in input order, returning results aligned to your coordinates.

Instructions

Compare GSI elevations for 1 to 10 supplied WGS84 points in input order.

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_elevations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description still adds real behavioral content beyond them: the coordinate reference system (WGS84), the batch ceiling of 10, and the guarantee that results follow input order.

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 sentence with no filler; the key constraint (1 to 10), the CRS, and the ordering behavior are all front-loaded and none of the wording is redundant.

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?

A one-parameter batch read with full annotations and an output schema, so return values and safety need no prose. The only residual gap is that units/vertical datum of the elevations are left to the output schema, which is a reasonable division of labor.

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 description coverage is 0% — the schema only says latitude/longitude are numbers with ranges. The description compensates by fixing the CRS as WGS84, clarifying that points are an ordered array, and restating the 1-10 bound, which the schema does enforce but does not explain.

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?

States a specific verb and resource ('Compare GSI elevations') and scopes it to a batch of 1-10 WGS84 points, which implicitly distinguishes it from the singular sibling get_elevation. It stops short of naming that alternative, so an agent must infer the split.

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 batch scope (1 to 10 points) implies this is the tool for multi-point comparisons, but there is no explicit 'use this instead of get_elevation when...' statement or any exclusion. Usage is inferable, not stated.

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