QuickBuild token-saver tools + x402

Base block lookup (latest/finalized/number/hash)

base_block

Read-onlyIdempotent

[PAID $0.001 USDC per call via x402 on Base; errors are free] Block header for Base mainnet (chain 8453) from public Base RPC: block number, hash, parent hash, timestamp, age in seconds, confirmations vs current head, transaction count, gas used/limit/utilization, base fee (gwei), fee recipient and size. block = latest (default), safe, finalized, a decimal or 0x-hex block number, or a 0x 32-byte block hash. Useful to check chain liveness/finality or timestamp an event before paying for /api/base/gas or /api/base/tx. Head tags cached 2 s, historical blocks 1 h. Invalid input = 400, unknown block = 404, never charged.

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

Input Schema

Name	Required	Description	Default
`block`	No	latest (default) \| safe \| finalized \| block number (decimal or 0x hex) \| 0x block hash

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond annotations by disclosing pricing ($0.001 USDC per call, errors free), caching behavior (head tags 2 s, historical blocks 1 h), and error semantics (400 invalid input, 404 unknown block, never charged). This gives an agent the cost and failure model it needs before calling.

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?

Front-loads the pricing and purpose, then packs return fields, parameter formats, use cases, caching, and errors into one strong paragraph. It is dense but each sentence contributes; slight gains possible from tighter formatting.

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?

With no output schema, the description compensates fully by listing all returned header fields, chain/source details, caching, error behavior, and pricing. An agent has everything needed to invoke and interpret the tool correctly.

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?

The input schema already documents the block parameter at 100% coverage, including the latest/safe/finalized/number/hash options. The description restates the same formats and notes 'latest (default)', adding little beyond the schema, so the baseline 3 applies.

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: 'Block header for Base mainnet (chain 8453) from public Base RPC', and enumerates returned fields. It is clearly distinguishable from siblings like base_gas_price and base_tx_status, which it references.

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?

Gives explicit usage context: 'Useful to check chain liveness/finality or timestamp an event before paying for /api/base/gas or /api/base/tx', naming alternatives and when to prefer them. It lacks an explicit 'when not to use' exclusion, so it falls just short of the top score.

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

All QuickBuild token-saver tools + x402 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?