Skip to main content
Glama

get_elevation

Read-onlyIdempotent

Reads GSI elevation in metres and returns its measurement source for a WGS84 latitude/longitude point, supporting ground-height checks at Japanese coordinates.

Instructions

Read the GSI elevation in metres and its measurement source at a WGS84 point.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_elevation"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYes
longitudeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile needs no restating. The description's genuinely additive information is that results are in metres and that a measurement source accompanies the value, which matters for judging data reliability. It says nothing about accuracy limits, coverage, or failure modes for out-of-coverage points.

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 tight sentence with the verb and returned values front-loaded and no filler. Every clause (GSI, metres, source, WGS84 point) carries information an agent needs.

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?

With only two self-evident parameters and an output schema covering return values, this sentence supplies enough to call the tool correctly. The remaining gap is tool selection against the plural sibling, which the description never resolves.

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 0%, but latitude and longitude are self-describing with min/max bounds. The description's real contribution is fixing the expected datum as WGS84, which is not stated in the schema. It adds no detail on ordering, accepted precision, or null returns for invalid coordinates.

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 has a specific verb plus resource ('Read the GSI elevation') and adds units (metres), a coordinate datum (WGS84 point), and the extra return field (measurement source). It stops short of distinguishing itself from the sibling get_elevations (plural), leaving the single-point vs. batch distinction to be inferred from the wording.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative, even though get_elevations is an obvious sibling for bulk lookups. The only hint is the implicit 'at a WGS84 point' scoping, which an agent must interpret on its own.

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