Skip to main content
Glama

Agent Exchange store

earth_snapshot

$0.01 via x402: Satellite snapshot (PNG) of the area around lat,lon on a date: NASA GIBS true-color imagery (MODIS Terra by default; VIIRS, Aqua and false-colour bands 7-2-1 on request), km half-width 2 to 500, up to 1024 px. For agents that watch places: ports, farms, fires, floods, construction, shipping. Pay 0.01 USDC per snapshot through https://store.agentexchange.work/gw/earth/snapshot. Via the Agent Exchan

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

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

A3.8/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 on the highest-risk trait: it discloses the $0.01 USDC x402 cost, the payment gateway, and that no payment yields a price response. It is silent on latency, caching, and error behavior, and the trailing sentence is cut off ('Via the Agent Exchan'), leaving the last point incomplete.

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?

Cost and resource are front-loaded, which is good, but the body is a dense run-on that packs defaults, alternatives and use cases into two long sentences, and the final sentence is truncated mid-word. The truncation and over-stuffing both cost it.

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?

For a paid image tool with no output schema, the description covers the return type (PNG), resolution ceiling, imagery lag, and the payment handshake, which is most of what an agent needs. Missing details are secondary: error/timeout behavior and how a retry after payment is handled.

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 lat, lon, km, date, size, layer and x_payment with ranges and defaults. The description restates km range, pixel cap, and layer names rather than adding syntax or format meaning, so the baseline 3 is appropriate.

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 with scope: a PNG satellite snapshot of the area around lat,lon on a date, with named imagery sources (NASA GIBS MODIS Terra by default). It clearly separates itself from earth_geocode and earth_reverse, but never distinguishes itself from the sibling earth_snapshot_json, which is the closest alternative.

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 concrete application context ('agents that watch places: ports, farms, fires, floods, construction, shipping'), which tells an agent when this tool is the right one. It does not state when NOT to use it or point to earth_snapshot_json for metadata-only needs, so it falls short of explicit routing.

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