Skip to main content
Glama

Web and geo tools (x402)

earth_snapshot_json

$0.005 via x402: Metadata for a satellite snapshot of lat,lon on a date: the bounding box, the imagery layer and date actually served, the pixel size, the NASA GIBS source URL and attribution, plus the paid PNG URL. Pay 0.005 USDC through https://store.agentexchange.work/gw/earth/snapshot.json. 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_snapshot_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
kmNohalf-width of the view in km, 2..500 (default 20)
latYeslatitude -90..90
lonYeslongitude -180..180
dateNoYYYY-MM-DD (default yesterday UTC; MODIS and VIIRS imagery lags about a day)
sizeNopixels per side, 128..1024 (default 512)
layerNotrue-color (default), viirs, aqua, bands721
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

B3.4/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 exact price ($0.005 USDC), the payment protocol (x402), the payment URL, the settlement party (Coinbase), and the gateway. The remaining gap is failure/timeout behavior and whether the payment is consumed on error, but the commercial and auth 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.

Conciseness3/5

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

Front-loaded with cost and purpose, which is good, but the price is stated twice ('$0.005 via x402' and 'Pay 0.005 USDC') and the payment URL is duplicated, and the trailing 'Via the Agent Exchange store gateway; settled by Coinbase' sentence is largely redundant with the payment URL context.

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 no annotations, yet the description enumerates the return payload (bounding box, served layer and date, pixel size, GIBS source URL and attribution, PNG URL), which compensates well. Only error/payment-failure semantics are absent.

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 schema already documents km, lat, lon, date, size, layer, and x_payment with ranges and defaults. The description adds no syntax or format detail beyond the schema, so baseline 3 applies.

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+resource ('Metadata for a satellite snapshot of lat,lon on a date') and enumerates the returned fields, so the agent knows this is the JSON metadata endpoint rather than the imagery itself. It does not explicitly name the sibling earth_snapshot (the PNG tool it references only via 'the paid PNG URL'), so sibling differentiation is implied rather than stated.

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

Usage Guidelines2/5

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

The description explains the payment mechanics but gives no guidance on when to choose this over earth_snapshot, earth_geocode, or earth_reverse, and no exclusions or preconditions beyond 'pay 0.005 USDC'. Usage is left entirely to inference from the field list.

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