Skip to main content
Glama

Get elevation at a point

get_elevation
Read-only

Returns terrain elevation in metres above sea level for WGS84 coordinates in Switzerland. Use it to look up ground height at a given latitude and longitude.

Instructions

Return the terrain elevation in metres above sea level for WGS84 coordinates in Switzerland.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "get_elevation"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude (Switzerland: ~45.8–47.9)
lonYesWGS84 longitude (Switzerland: ~5.9–10.6)

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 declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context beyond them: units (metres above sea level), the WGS84 datum, and a hard geographic restriction to Switzerland, which tells the agent when calls will legitimately return nothing.

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 front-loaded sentence that names the return value, its unit, the accepted coordinate system, and the coverage area with no wasted words.

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 two-parameter read-only lookup with full schema coverage and no output schema, this covers the essentials: what is returned, in what unit, for what input datum, and within what region. Only the return shape (scalar number vs. object) is left unstated, a minor gap.

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%, with both lat and lon documented and bounded, so the schema does the heavy lifting. The description only restates the datum and country, adding no format, precision, or edge-case guidance beyond what the schema already provides.

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 ('Return the terrain elevation') with units, coordinate datum, and geographic scope. It does not distinguish itself from the sibling get_elevation_profile, so an agent must infer the single-point vs. profile split on its own.

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?

Usage is implied: 'WGS84 coordinates' (a single pair) and a Switzerland bounding scope suggest one-point queries, and that scope implicitly excludes out-of-country calls. There is no explicit when-to-use, when-not-to-use, or pointer to get_elevation_profile for sampled paths, even though that sibling is the obvious alternative.

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