SiteCheck Crypto & Finance

Ethereum EIP-1559 gas per recent block: base fee, gas used

crypto_ethereum_gas_telemetry

Read-only

Ethereum EIP-1559 gas per recent block: base fee (gwei), gas used ratio, and priority fee (tip) percentiles at 10/50/90 from eth_feeHistory, plus the next block's base fee. Gas used by contract is not included (this RPC does not give it). Related tools on this server, for a different need: crypto_ethereum_staking_rewards when you need Ethereum proof-of-stake yield snapshot: Lido stETH APR. 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_ethereum_gas_telemetry"
  }
}

Input Schema

Name	Required	Description	Default
`blockCount`	No	How many recent blocks, 1 to 20 (default 5)

Output Schema

Name	Required	Description	Default
`blocks`	No
`source`	No
`checkedAt`	No
`blockCount`	No
`oldestBlock`	No
`nextBaseFeeGwei`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, it discloses the underlying eth_feeHistory source, exact returned metrics, a key limitation that contract gas usage is unavailable, and the x402 payment model with failed calls not charged.

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 purpose and returned metrics are front-loaded and clear. Pricing and sibling cross-reference are useful but make the definition denser than strictly necessary.

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?

For a one-parameter read-only telemetry tool with an output schema, annotations, and full parameter coverage, the description covers source, scope, limitations, and cost sufficiently for correct invocation.

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 single blockCount parameter already has 100% schema description coverage with range and default. The description adds no additional parameter-specific meaning beyond referring to recent blocks, so the schema does the heavy lifting.

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?

Opens with a specific resource and scope, Ethereum EIP-1559 gas per recent block, and enumerates returned metrics including base fee, gas used ratio, priority-fee percentiles, and next block base fee. This clearly distinguishes it from siblings such as crypto_ethereum_staking_rewards.

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?

Explicitly redirects staking-yield needs to crypto_ethereum_staking_rewards and notes that contract-level gas usage is not included. It does not provide broader when-not-to-use guidance across the many other crypto data tools, but the relevant alternative is named.

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?