Skip to main content
Glama

Web and geo tools (x402)

earth_geocode

$0.002 via x402: US address to coordinates: one-line address in, matched address, longitude/latitude, tiger line id and side out, from the US Census Bureau geocoder (public domain, current benchmark). Pay 0.002 USDC through https://store.agentexchange.work/gw/earth/geocode?address=... 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": {
      "address": "<address>"
    },
    "name": "earth_geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesone-line US address, e.g. 1600 Pennsylvania Ave NW, Washington, DC
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.9/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 behavioral burden and does well: it discloses the $0.002 x402 price, the USDC payment path, the gateway/settlement provider, and the data source (US Census Bureau, public domain). Rate limits and error behavior are unstated, but the auth/payment profile is unusually well covered.

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?

The cost and purpose are front-loaded and the whole definition is compact. It slightly wastes space by stating the price twice ('$0.002 via x402' and 'Pay 0.002 USDC'), and the run-on output list is dense, but nothing is gratuitous.

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?

There is no output schema, and the description responsibly enumerates the return fields (matched address, lon/lat, tiger line id/side). For a two-parameter tool it is nearly self-sufficient; only error/edge-case behavior is missing.

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%, so the schema already documents both 'address' and 'x_payment' (including the price-fallback behavior). The description only echoes the one-line address format and the payment requirement, adding little beyond the structured fields, so the baseline 3 holds.

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?

The description states a precise verb and resource: 'US address to coordinates,' and enumerates the outputs (matched address, longitude/latitude, tiger line id and side). The forward-geocoding scope is inherently distinct from the reverse sibling (earth_reverse) without needing to name it.

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?

It implies when the tool applies (US one-line address lookup) and notes the payment prerequisite, but never names alternatives or contrasts against earth_reverse/earth_snapshot. Usage context is present but left to inference.

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