Skip to main content
Glama

Agent Exchange store

signals_quakes

$0.002 via x402: Earthquakes from the USGS feed: magnitude, place, time, depth, coordinates, tsunami flag, link; filter by minimum magnitude (1.0, 2.5, 4.5) and window (hour, day, week). Pay 0.002 USDC through https://store.agentexchange.work/gw/signals/quakes?min_mag=4.5&window=day Via the Agent Exchange store gateway; settled by Coinbase.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "signals_quakes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1..200, default 50
windowNohour, day or week (default day)
min_magNo1.0, 2.5 or 4.5 (default 2.5)
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.6/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 disclose the critical behavioral trait: this is a paid x402 endpoint costing 0.002 USDC settled by Coinbase, and the schema notes that without x_payment the response is just the price. That is a genuinely important non-obvious behavior; rate limits, error modes and response format are still unstated.

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?

One long run-on sentence with an embedded full payment URL and query-string example. It front-loads the price, but '$0.002 via x402' and 'Pay 0.002 USDC' are redundant, and the URL clutters the middle of the sentence.

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, so listing the returned fields is necessary and done well; payment mechanics are covered. What is missing is a short statement of response shape/format and any usage constraints, but for a simple read-only data feed this is close to sufficient.

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 limit/window/min_mag/x_payment are already documented in the schema. The description restates the filter values but adds no syntax or format detail beyond what the schema provides — baseline 3.

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 concrete verb+resource — 'Earthquakes from the USGS feed' — and enumerates the returned fields (magnitude, place, time, depth, coordinates, tsunami flag, link) plus the two filter axes. This is specific enough to separate it from earth_geocode, weather_forecast and the other signals_* tools, though it never names a sibling 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?

The description gives filter values (min_mag 1.0/2.5/4.5, window hour/day/week), which implies how to narrow a query, but never states when to prefer this feed over alternatives or what prerequisites (funded wallet, gateway) must be met. Usage is inferred rather than prescribed.

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