Skip to main content
Glama

BRAINIAC Base Chain Data

Get fee history

chain-data_gas_fee-history

Retrieve the fee history for Base Mainnet blocks, including base fees and reward percentiles. Supports EIP-1559. Price $0.03 USDC. POST /api/v1/chain-data/gas/fee-history. Unpaid calls return 402 and do not run.

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": "chain-data_gas_fee-history"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockCountNo
newestBlockNo
rewardPercentilesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load, and it does add useful operational context: the $0.03 USDC price, the POST endpoint, and that unpaid calls return 402 without executing. It does not disclose rate limits, pagination, or the response shape beyond naming base fees and reward percentiles.

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?

Four short sentences, front-loaded with what is retrieved, then pricing and endpoint, then the payment failure mode. Efficient and readable, though the endpoint path is low-value filler for an agent that already routes by tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with no annotations and no output schema, the definition covers cost and failure behavior but leaves parameter semantics and return format largely unspecified. An agent knows what it gets conceptually but not how to size or target the request.

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 description coverage is 0% across three parameters (blockCount, newestBlock, rewardPercentiles), so the description would need to compensate. It only alludes to reward percentiles as part of the output and never explains blockCount, newestBlock, defaults, or the 1024-block cap.

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?

The description states a specific verb and resource ('Retrieve the fee history for Base Mainnet blocks') plus the payload contents (base fees, reward percentiles) and EIP-1559 support. It does not name or contrast with any sibling such as chain-data_gas_estimate, so differentiation is left to the reader.

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 purpose and by notes on pricing and 402 behavior, but there is no explicit when-to-use or when-not-to-use guidance. In particular it never says how this differs from the sibling gas_estimate tool or when a fee history is preferable.

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