Skip to main content
Glama

Recent Earthquakes Payment Quote

earthquakes_recent_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/earthquakes/recent (base $0.002; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?hours=24&minmag=4.5 (hours 1-720, minmag -1 to 10; optional lat, lon and radiusKm 1-2000 together, limit 1-500, order=time|magnitude). 404 no_events = valid empty result, not charged.. Recent earthquakes: up to 500 USGS catalog events from the last 1 to 720 hours, by minimum magnitude and optional point and radius. Returns id, magnitude, place, time, coordinates, depth, review status, PAGER alert, tsunami flag and USGS event link, newest or largest first. Data: U.S. Geological Survey (public domain). Not a warning service. No events, bad input or source down: not charged. USDC on Base only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: exact price ($0.002 base), currency and chain constraint (USDC on Base only), the x402 v2 payment protocol, and a charging policy (404 no_events, bad input, source down are not charged). 'Not a warning service' is a useful expectation-setting caveat that annotations could never convey.

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 front-loaded: purpose, price, payment mechanics, parameters, then data description. Minor deductions for a stray double period ('not charged..'), a mid-sentence sentence break at 'not charged.. Recent earthquakes', and repeating 'USDC on Base only' twice.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter quote tool with no output schema, the description covers everything an agent needs: price and currency, payment endpoint and protocol, full query parameter ranges, the returned field list (id, magnitude, place, time, coordinates, depth, review status, PAGER alert, tsunami flag, link), sort order, and charge/error semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is empty, so the description must carry the query semantics, and it does: hours 1-720, minmag -1 to 10, lat/lon with radiusKm 1-2000 required together, limit 1-500, order=time|magnitude, plus a concrete default example (hours=24&minmag=4.5). This is meaningfully more than an empty schema provides.

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?

States a specific verb and resource — 'Returns the payment terms for https://horizonpulse.dev/api/earthquakes/recent' — and immediately scopes it with 'this tool never runs the check or pays', which is the exact distinction an agent needs against the actual data-fetch step. The data description (up to 500 USGS catalog events, last 1-720 hours) confirms what the paid endpoint yields, so the purpose is unambiguous.

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?

Explains the workflow clearly: call this to obtain terms, then 'Pay the 402 over HTTP with x402 v2: GET ?hours=24&minmag=4.5'. It also gives the fallback conditions (no_events 404 is a valid empty result, bad input or source down are not charged). It does not name specific alternative siblings for related data, but the quote-then-pay pattern is explicit rather than implied.

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.