Skip to main content
Glama

Agent Exchange store

earth_reverse

$0.002 via x402: US coordinates to geographies: state, county, place, census tract and block, congressional and state legislative districts, urban area, with FIPS/GEOID codes, from the US Census Bureau geocoder (public domain). Pay 0.002 USDC through https://store.agentexchange.work/gw/earth/reverse?lat=...&lon=... Via the Agent Exchange store gateway; settled by Coinbase.

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

Input Schema

NameRequiredDescriptionDefault
latYeslat
lonYeslon
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the cost ($0.002 USDC), the payment protocol (x402 via the Agent Exchange store gateway, settled by Coinbase), the auth requirement, and the data provenance (US Census Bureau geocoder, public domain). It omits rate limits and error behavior, keeping it short of a 5.

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?

Dense but earns its words — purpose, coverage list, source, and payment mechanics are all relevant. The payment URL and gateway details are slightly verbose and partially redundant with the tool name, but the geography enumeration is front-loaded and useful.

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?

No output schema exists, and the description compensates by enumerating the returned geographies and code systems. Payment/auth requirements are fully covered. For a two-input geocoding tool this is nearly complete, missing only response shape details like precision or null handling for non-US coordinates.

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%, so the baseline is 3. The description adds no syntactic detail for lat/lon beyond the schema, and the x_payment semantics ('without it the answer is the price') are already documented in the schema. The description does not compensate with additional format or range guidance.

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 specifies the transformation precisely: 'US coordinates to geographies', then enumerates the exact outputs (state, county, place, census tract and block, congressional and state legislative districts, urban area) with FIPS/GEOID codes. The coordinate→geography direction inherently distinguishes it from the forward geocoder sibling (earth_geocode), though no sibling is named explicitly.

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 input/output mapping (pass lat/lon, receive geography codes), and the description makes clear this is a US-only reverse lookup. However, it never states when to prefer this over earth_geocode or other earth_* siblings, nor any exclusions. Adequate but with a clear gap.

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