Skip to main content
Glama

x420_chain_gas-estimate

Estimates Base mainnet gas prices and EIP-1559 fees, with reference ETH and ERC-20 transfer costs, and optionally calculates estimateGas for a custom call using to, value, and data.

Instructions

Base gas estimate: Current Base mainnet gas price, EIP-1559 fee estimate and base fee, reference costs for an ETH transfer and a typical ERC-20 transfer, and optionally an estimateGas for a call you describe (to, value, data). Source: Base mainnet RPC. L1 data fee not included. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.02 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: gas_price_gwei, max_fee_per_gas_gwei, base_fee_gwei, reference{eth_transfer, erc20_transfer_typical}, requested{estimate} - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {}.

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": "x420_chain_gas-estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNodestination address to estimate a call against (default: none)
dataNo0x calldata for the estimate (default: none)
fromNosender address for the estimate (default: none)
value_ethNoETH value for the estimate (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.1/5.0
Behavior5/5

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

It discloses critical behavior beyond the annotations: a $0.02 USDC paid call settled on Base via x402 from the configured wallet (real money), Base mainnet RPC as the source, exclusion of L1 data fees, and inclusion of a signed receipt and settlement transaction in the response. This is consistent with the non-read-only annotation caused by payment/settlement.

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 purpose and return information are front-loaded, and the detail is mostly useful for a paid tool. However, it is a dense single run-on passage with a long legal disclaimer that could be structured more cleanly.

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 explains the return JSON fields, signed receipt, settlement transaction, source limitation, and example input. It provides enough information for an agent to call the tool and understand what comes back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all four parameters, including from. The description adds useful framing that to/value/data are for an optional estimateGas call, but it omits from and does not add format or syntax details beyond the schema.

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 resource and scope: current Base mainnet gas price, EIP-1559 fee and base fee, reference ETH/ERC-20 transfer costs, and optional estimateGas for a described call. It is clearly a gas-estimation tool, though it does not explicitly distinguish itself from sibling chain tools.

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?

It gives clear usage context: retrieve Base gas estimates, with an optional per-call estimateGas via the to/value/data parameters. It does not name when-not-to-use cases or explicit alternatives, but the context is sufficiently clear.

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