Agent Weather

Base latest block (paid: 0.001 RLUSD / 0.001 USDC on Base / 0.001 RLUSD on Base via x402)

base_block_tip

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: What is Base's latest block number and timestamp? 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

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

Input Schema

Name	Required	Description	Default
`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

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint false, and destructiveHint false. The description adds essential behavior beyond that: exact pricing, accepted payment networks, unpaid-call behavior, the fresh invoiceId on PaymentRequired, the retry mechanism, and the fact that unpaid calls cost nothing.

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?

The description is front-loaded with price, purpose, and payment flow, and every sentence contributes to calling the tool correctly. There is minor redundancy with the title's pricing text and some repetition around 'paid' and 'per call', but it remains easy to scan.

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?

With no output schema, the description carries responsibility for explaining success and failure behavior. It clearly states the question answered and the unpaid error/retry flow, though it does not describe the exact successful response payload or any freshness/caching semantics.

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

Parameters4/5

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

Schema coverage is 100%, so the single payment_signature parameter is already documented. The description adds useful operational meaning by explaining that the signed payload can be supplied via _meta["x402/payment"] or the payment_signature argument when retrying after PaymentRequired.

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?

The description states a specific resource and scope: Base's latest block number and timestamp. It is easy to distinguish from siblings such as base_gas_fees because it clearly frames the tool as answering one narrowly defined question.

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?

The description gives clear context for when to use the tool: a paid per-call query for Base's latest block. It does not explicitly compare against alternatives or state exclusions, so it stops short of full when/when-not routing guidance.

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?