Skip to main content
Glama

ethereum-fee-snapshot

Ethereum mainnet fee reference. A static snapshot captured 2026-11-14, no input: the EIP-1559 execution fee rules (12.5 percent base-fee steps toward the half-limit target), the EIP-4844 blob market (6 target, 9 max per block), the observed 0.445 gwei base-fee reference with the 2026 sub-gwei era, and transfer, ERC-20, and swap cost scenarios computed at those reference levels, the capture date printed on every card. Price: $0.01 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": "ethereum-fee-snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

No annotations exist, and the description carries the full burden well. It discloses the data is a static snapshot with a fixed capture date (a staleness caveat), that there is no input, that cost is $0.01 per call in USDC on Base via x402, and that an unpaid call returns HTTP 402 with machine-readable payment terms — behavior an agent cannot get from structured fields.

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?

The lead sentence is well front-loaded, but the remainder is one dense run-on packing protocol details (12.5 percent steps, 6 target / 9 max blobs) that add little to tool selection. Splitting contents, capture date, and payment terms into short clauses or bullets would read faster without losing information.

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 must describe what comes back, and it does — enumerating the fee rules, blob market figures, 0.445 gwei base-fee reference, cost scenarios, and the capture date printed on every card. Payment mechanics are also covered, so an agent knows what it receives and what it costs before calling.

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?

The schema has zero parameters at 100% coverage, so baseline is 4. The description reinforces this with 'no input,' preventing an agent from inventing optional filters, but there is nothing further to clarify about parameter meaning.

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?

Front-loads a precise scope: 'Ethereum mainnet fee reference. A static snapshot captured 2026-11-14, no input.' The chain qualifier alone separates it from the arbitrum/base/optimism/polygon fee-snapshot siblings, and the enumerated contents (EIP-1559 rules, EIP-4844 blob market, base-fee reference, transfer/ERC-20/swap scenarios) make the payload unambiguous.

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?

Usage is implied by the chain scoping and the 'no input' note, which tells the agent this is a zero-argument lookup. However, it never states when to prefer this over a sibling chain snapshot or when the 2026-11-14 capture date makes it unsuitable for live fee decisions; the agent must infer both from labels.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources