Agent Weather

Changes since last check (paid: 0.001 RLUSD / 0.001 USDC on Base / 0.001 RLUSD on Base via x402)

readings_changes

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: How have selected Agent Weather snapshot metrics changed since a cursor? 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": {
      "since": "<since>"
    },
    "name": "readings_changes"
  }
}

Input Schema

Name	Required	Description
`since`	Yes
`metrics`	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

A3.7/5.0

Behavior5/5

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

Beyond the annotations, it discloses the pay-per-call cost, that unpaid calls return isError with a x402 PaymentRequired object containing a fresh invoiceId, that retry requires the signed payload in _meta["x402/payment"] or payment_signature, and that failed unpaid calls are free. That is the exact operational behavior an agent needs and is not derivable from readOnlyHint/destructiveHint.

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?

Pricing is front-loaded ahead of the actual purpose, and the title duplicates the per-chain price list almost verbatim. Sentences are dense but each carries information; the ordering just prioritizes billing over what the tool does.

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

Completeness3/5

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

With no output schema and two undocumented parameters, the definition should say what the change payload looks like and how cursors are obtained. The payment and error path is fully covered, but the core data contract for a 3-parameter tool remains incomplete.

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 coverage is only 33%: payment_signature is documented in the schema, and the description clarifies the payment flow, but 'since' (cursor format) and 'metrics' (allowed metric names/format) receive no meaning from either source. It adds some value on payment plumbing but leaves the two core query parameters opaque.

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 question the tool answers: how selected Agent Weather snapshot metrics have changed since a cursor. That is a clear verb-plus-resource purpose, though it never names the sibling tools (get_merchant_readings, batch_readings, get_current_conditions) it is distinct from.

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 implies usage via 'since a cursor' and gives a detailed payment/retry procedure, but it never says when to pick this over the sibling readings tools or when a cursor is valid. The when-to-use guidance is inferred rather than stated.

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?