Skip to main content
Glama

X420 agent services

x420_geo_elevation

Read-onlyIdempotent

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. Price: $0.02 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: elevation, units, resolution_m, raster_id.

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 observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the price ($0.02 USDC on Base), the critical fact that this hosted tool does NOT return the deliverable, and the exact x402 handshake (GET url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE). It also names the escape hatch of running the local x420-mcp server with a wallet key, which an agent could not infer from readOnlyHint/idempotentHint alone.

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?

Purpose and source are front-loaded, and the payment mechanics are ordered as a usable sequence. The blanket 'not professional, legal, insurance, engineering, medical, financial or tax advice' sentence is boilerplate that dilutes an otherwise tight definition.

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?

With no output schema, the description compensates by enumerating the paid deliverable fields and by spelling out the two-step payment protocol and the local-server fallback. Coverage limits, accuracy caveats and cost are all present, leaving nothing an agent needs in order to call it correctly.

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% and the schema already documents lat, lon and the feet/meters units option, so the description adds no parameter-level meaning. The field list at the end (elevation, units, resolution_m, raster_id) describes the deliverable, not the inputs, so baseline 3 applies.

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 ('Ground elevation at a coordinate') plus the exact upstream source (USGS 3DEP EPQS), which cleanly separates it from siblings like x420_geo_distance, x420_geo_flood-zone and x420_geo_geocode. An agent can identify the tool without opening the schema.

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

Usage Guidelines4/5

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

Gives a clear applicability boundary ('US coverage; a DEM sample, not a survey') and a full invocation path for the paid flow, including the local-server alternative. It does not explicitly name a sibling or state when a different geo tool should be chosen instead, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources