Skip to main content
Glama

base-fee-snapshot

Live Base mainnet fee snapshot. The current gas price and base fee, the block number, the base-fee window over the last 20 blocks (average, low, high) with trend and congestion labels, in wei and gwei, every card stamped with its as-of time. Descriptive network data, not trade advice. Price: $0.05 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": "base-fee-snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the $0.05 USDC price on Base via x402 and that an unpaid call returns HTTP 402 with machine-readable payment terms. It stops short of stating rate limits, latency, or whether repeated calls are cached, which keeps it below a 5.

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 leads with what the call returns, then adds the scope caveat, then the pricing/error mechanics — a sensible front-loaded order. It is dense but every sentence carries information; only the wei/gwei and labeling detail borders on listing output fields at length.

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?

There is no output schema, so the description must convey the return shape, and it does: price fields, block number, window averages/low/high, trend and congestion labels, units, and per-card as-of timestamps. Combined with the payment and 402 behavior, an agent has everything needed to call it and interpret the result.

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 tool takes zero parameters, so there is nothing to document and the schema already reflects that; a baseline 4 applies. The description usefully confirms the no-input nature by describing a fixed network snapshot rather than a queryable resource.

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 resource and scope: a live Base mainnet gas price / base fee snapshot, with the exact fields returned (gas price, base fee, block number, 20-block window). Naming Base mainnet distinguishes it from the arbitrum/ethereum/optimism/polygon fee-snapshot siblings without opening any schema.

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?

Frames the use case clearly ('live snapshot', 'descriptive network data, not trade advice') and explains the payment precondition, so an agent knows it is a paid read of current network state. It does not explicitly route to the other chain snapshots, but the chain is named up front, so selection is inferable.

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