Skip to main content
Glama

BRAINIAC Base Chain Data

Estimate gas for transaction

chain-data_gas_estimate

Estimate the gas required for a transaction on Base Mainnet using eth_estimateGas. Price $0.02 USDC. POST /api/v1/chain-data/gas/estimate. 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_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
dataNo
fromNo
valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description usefully discloses Base Mainnet, the eth_estimateGas method, the $0.02 USDC price, and that unpaid calls return 402 without running. However, it does not clarify whether estimation has side effects, how failures or reverts are handled, or whether a failed estimate is still 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 description is short and front-loads the core purpose, network, and method. The pricing and 402 behavior are useful, while the raw POST endpoint is lower-value implementation detail for an agent.

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

Completeness2/5

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

For a tool with four undocumented optional parameters, no annotations, and no output schema, the description leaves important gaps. It does not explain the parameters or state what the gas estimate response contains, though it does cover payment and unpaid-call behavior.

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% for four parameters, so the description must compensate but does not explain the meaning or format of to, data, from, or value. Referencing eth_estimateGas and 'transaction' gives only weak implicit context about standard Ethereum transaction fields.

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: estimating gas for a transaction on Base Mainnet via eth_estimateGas. It is clearly distinct from sibling tools such as block or transaction receipt retrieval, though it does not explicitly name an alternative to differentiate itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains payment and endpoint mechanics but gives no guidance on when to use this tool versus siblings like gas fee-history or transaction receipt. There are no when-to-use or when-not-to-use conditions beyond the implied need for a gas estimate.

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