SiteCheck Crypto & Finance

OP Mainnet recent blocks from the public RPC: transactions

crypto_optimism_superchain_tx

Read-only

OP Mainnet (Optimism) recent blocks from the public RPC: transactions per block, gas used per block, block time, and the transaction rate over the last N blocks (1 to 10). Sequencer revenue and Superchain-wide totals are not in this RPC and are not reported. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not 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": "crypto_optimism_superchain_tx"
  }
}

Input Schema

Name	Required	Description	Default
`blocks`	No	How many latest blocks to read, 2 to 10 (default 5)

Output Schema

Name	Required	Description	Default
`blocks`	No
`source`	No
`checkedAt`	No
`txPerSecond`	No
`tipBlockNumber`	No
`avgBlockTimeSec`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the pricing model ($0.002 USDC per successful call via x402 on Base, Solana or Arc) and that failed calls are not charged — genuinely useful cost/risk context for an agent deciding whether to call. It does not describe latency or response shape, but an output schema exists to cover the latter.

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 the resource and metrics, then exclusions, then pricing — a sensible order with little waste. The pricing sentence is somewhat lengthy but carries decision-relevant information.

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?

For a single-parameter read tool with full schema coverage, an output schema, and safety annotations, the description supplies the remaining decision-relevant facts: network, metric set, exclusions, and cost. The only material gap is the parameter-range inconsistency, which undercuts otherwise complete coverage.

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 100%, so the schema already fully documents the single 'blocks' parameter, and the description adds no syntax or meaning beyond it. Worse, the description states a range of '1 to 10' while the schema specifies '2 to 10 (default 5)', creating a conflicting bound that could lead an agent to pass an invalid value.

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 names a specific chain (OP Mainnet/Optimism), a specific source (public RPC), and enumerates the exact metrics returned: transactions per block, gas used per block, block time, and transaction rate. No sibling tool targets OP Mainnet block data, so an agent can select this without ambiguity.

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 clearly scopes when this tool is and is not appropriate by stating that sequencer revenue and Superchain-wide totals are not in this RPC, steering the agent away for those needs. It does not, however, name an alternative tool for the excluded metrics.

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

All SiteCheck Crypto & Finance 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?