Skip to main content
Glama

optimism-fee-snapshot

OP Mainnet fee reference. A static snapshot captured 2026-11-14, no input: the fee model mechanics (EIP-1559 execution, the Ecotone L1 data fee formula with the documented 5227 and 1014213 scalars, the Isthmus operator fee) and the observed typical cost ranges from the 2026 trackers, the capture date printed on every card. The L1 data fee rides live Ethereum prices, so the card carries formulas and observed ranges, never fabricated totals. 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": "optimism-fee-snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With zero annotations the description carries the full burden and does substantial work: it discloses the billing model ($0.01 per call in USDC on Base mainnet over x402), the failure mode of an unpaid call (HTTP 402 returning machine-readable payment terms), and a data-vintage caveat that totals are never fabricated. Missing only what the response payload structurally looks like beyond 'cards' with formulas and a printed capture date.

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 snapshot nature and capture date are front-loaded, which is correct. But the second sentence is a long comma-spliced run that stacks pricing, payment protocol, and a 402 error path, and several parenthetical scalar numbers are dense without aiding tool selection. Information earns its place but the packaging is heavy.

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 must convey return content, and it does: fee formulas, observed typical cost ranges from 2026 trackers, and a capture date printed on every card. It also covers cost and the payment-required path. For a zero-parameter reference tool this is nearly complete, lacking only a note on card granularity or structure.

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?

Zero parameters, so the baseline applies. The description still explicitly confirms 'no input', which reassures the agent that an empty object schema is intentional rather than a truncated definition. No parameter meaning is left ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States concretely what the tool returns: OP Mainnet fee mechanics (EIP-1559 execution, Ecotone L1 data fee formula with 5227/1014213 scalars, Isthmus operator fee) plus observed cost ranges. The chain name and 'static snapshot' scope distinguish it from base-fee-snapshot and ethereum-fee-snapshot without needing to name them. It stops short of an explicit verb like 'returns'/'fetches', so it is clear rather than exemplary.

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?

'No input' and the fixed capture date 2026-11-14 tell the agent when the data applies, and the note that the L1 data fee rides live Ethereum prices implies the card is a reference, not a live quote. However there is no explicit when-to-use/when-not statement and no routing to or away from the sibling snapshot tools. Usage is implied rather than prescribed.

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