Agent Weather

USGS earthquakes near a point (paid: 0.001 RLUSD / 0.001 USDC on Base / 0.001 RLUSD on Base via x402)

usgs_earthquakes

Read-only

Paid: 0.001 RLUSD per call via x402 on XRPL mainnet (xrpl:0), or 0.001 USDC on Base (eip155:8453). Pay per call, solves one question: Which USGS earthquake events are near this point? Pass-through public USGS fields with credit. Without payment this returns isError with the x402 PaymentRequired object (fresh invoiceId); retry with the signed payload in _meta["x402/payment"] or the payment_signature argument. Unpaid calls cost nothing.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "usgs_earthquakes"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`latitude`	Yes
`longitude`	Yes
`maxradiuskm`	No
`minmagnitude`	No
`payment_signature`	No	Optional. Base64 x402 PAYMENT-SIGNATURE value (signed RLUSD or USDC PaymentPayload) for hosts that cannot set _meta["x402/payment"]. Omit on the first call to receive the payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations only declare readOnly/openWorld/non-destructive; the description adds genuinely non-obvious behavior: unpaid calls return isError carrying a PaymentRequired object with a fresh invoiceId, unpaid calls cost nothing, and the two accepted payment channels/asset types. It does not describe the result payload shape or any rate limits.

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?

It is front-loaded with pricing and payment mechanics rather than what the tool retrieves, which is the least useful ordering for tool selection. Sentences are individually dense and non-redundant, but roughly half the text serves the payment protocol rather than the query semantics.

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, yet the payment path is described thoroughly enough for an agent to complete a paid call (invoice, signature placement, retry, cost). The remaining gap is the return payload ('pass-through public USGS fields' is vague) and the undocumented query parameters, which is a real but secondary omission.

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

Parameters2/5

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

Schema coverage is 17% — only payment_signature is documented. The five domain parameters (latitude, longitude, limit, maxradiuskm, minmagnitude) are bare untyped strings with no schema descriptions, and the description adds no units, formats, defaults, or valid ranges (degrees vs. km, magnitude scale, string-encoded numbers despite additionalProperties:false).

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?

The description states a specific verb and resource via the framing question 'Which USGS earthquake events are near this point?' and notes it is a pass-through of public USGS fields. It is distinguishable from every sibling (none of which are seismic-query tools), though the purpose sentence is buried behind a pricing preamble.

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 gives real procedural guidance for the x402 flow: call unpaid first, receive PaymentRequired, then retry with a signed payload in _meta["x402/payment"] or payment_signature. It says nothing about when this tool is preferable to alternatives, nor how to choose radius/magnitude limits or what defaults apply.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Weather tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?