Skip to main content
Glama

x420_geo_elevation

Get ground elevation at a latitude/longitude coordinate from USGS 3DEP point data, returning elevation, units, and resolution for U.S. locations.

Instructions

Elevation at a point: Ground elevation at a coordinate from the USGS 3D Elevation Program point query service (free, no key). Source: USGS 3DEP EPQS. US coverage; a DEM sample, not a survey. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.02 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: elevation, units, resolution_m, raster_id - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"lat":"32.7357","lon":"-97.1081"}.

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": "x420_geo_elevation"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYeslatitude
lonYeslongitude
unitsNofeet (default) or meters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only say readOnly=false, openWorld=true, idempotent=false, destructive=false; the description adds far more: a metered $0.02 USDC charge per call on Base via x402, the wallet env var that funds it, real-money settlement, and that each call returns a signed receipt plus the settlement transaction. Together these explain why readOnly is false and why the call is not idempotent. What is missing is what happens when payment fails or the point falls outside US coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then source, coverage caveats, payment terms, return shape, and an example — a sensible order. The run-on disclaimer list ("professional, legal, insurance, engineering, medical, financial or tax advice") is boilerplate that costs more space than it earns for a paid elevation lookup.

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?

No output schema exists, yet the description enumerates the return fields (elevation, units, resolution_m, raster_id, plus receipt and settlement tx), and it discloses cost, currency, chain, wallet prerequisite, and data-source caveats. For a 3-parameter paid lookup, an agent has everything needed to call it and interpret the result.

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 the baseline is 3; the description earns an extra point by giving a concrete example input that shows lat/lon are string-typed decimal degrees ("32.7357", "-97.1081"). It adds nothing about how 'units' interacts with 'resolution_m' in the response, so it does not go beyond a modest lift over the schema.

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?

States a specific verb and resource ("Elevation at a point: Ground elevation at a coordinate") and names the exact data source, USGS 3DEP EPQS. It also scopes the answer ("US coverage; a DEM sample, not a survey"), so an agent can tell at a glance that this is not the flood-zone, geocode, or distance sibling.

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 by the scope statements (US only, DEM sample, not a survey, not professional advice), which help an agent decide when the result is appropriate. However, there is no explicit routing guidance — nothing like "use x420_geo_geocode first if you only have an address" — and no stated error or out-of-coverage behavior.

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