Skip to main content
Glama

EVM & Solana Chain Reads (Tanod)

estimate_gas

Read-onlyIdempotent

chainpeek: Estimate the gas of a transaction on Ethereum, Base or Robinhood Chain. For the gas price use get_gas; for a whole transfer check use transfer_preflight. Returns the node's gas estimate (gas) for a transaction from from to to with data and value_wei, plus gas_with_20pct_buffer; omit to with data to estimate a contract creation. Nothing is signed or sent. Input: chain, to, optional from, data and value_wei; send to or data. Estimated at the latest block against current state, so the real cost can differ. A transaction that would revert is a 422 reverted (not charged). Ethereum, Base and Robinhood only; read-only: nothing is signed or sent. RPC reads are cached up to 30 s. A bad address, hash, hex string, block or range is a 422 before any payment (not charged). Typically under 1 s. Price: USD 0.002. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/ethereum-rpc-reads-api.html

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain": "<chain>"
    },
    "name": "estimate_gas"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoRecipient. Omit with `data` to estimate a contract creation.
dataNoCalldata, 0x-hex with an even number of digits, at most 8 kB.
fromNoSender (affects balance and allowance checks).
chainYesethereum, base or robinhood (Robinhood Chain, chain id 4663).
value_weiNoNative value in wei, as a decimal or 0x-hex string.

Output Schema

NameRequiredDescriptionDefault
toNo
gasNo
fromNo
noteNo
chainNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
contract_creationNo
gas_with_20pct_bufferNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedInput schema / properties / chain / title
      Removed value: -"Chain"
    • removedInput schema / properties / data / default
      Removed value: -null
    • removedInput schema / properties / data / title
      Removed value: -"Data"
    • removedInput schema / properties / from / default
      Removed value: -null
    • removedInput schema / properties / from / title
      Removed value: -"From"
    • removedInput schema / properties / to / default
      Removed value: -null
    • removedInput schema / properties / to / title
      Removed value: -"To"
    • removedInput schema / properties / value_wei / default
      Removed value: -null
    • removedInput schema / properties / value_wei / title
      Removed value: -"Value Wei"
    • removedInput schema / title
      Removed value: -"estimate_gasArguments"
  2. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"ethereum or base."New value: +"ethereum, base or robinhood (Robinhood Chain, chain id 4663)."
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "ethereum",
      -  "base"
      -]New value: +[
      +  "ethereum",
      +  "base",
      +  "robinhood"
      +]
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes well beyond them: the response fields (`gas`, `gas_with_20pct_buffer`), the fact that nothing is signed or sent, the 422 `reverted` outcome with no charge, cached RPC reads up to 30 s, sub-second typical latency, price, and the free-per-IP quota. It also warns that estimation happens against latest state so real cost can differ, which is genuinely useful behavioral context for a gas estimator.

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?

Front-loaded with purpose and alternatives, which is good, but there is visible redundancy: 'Nothing is signed or sent' appears twice, the chain list is repeated, and the not-charged/422 rule is stated twice. The pricing and quota tail is useful but adds bulk to an otherwise dense paragraph.

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?

For a paid, read-only RPC wrapper with an output schema, the description covers everything an agent needs before calling: required inputs, the to/data alternative, revert handling, invalid-input handling, latency, cost, and free quota. Nothing material is missing given the annotations and schema already supplied.

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?

Schema coverage is 100%, so baseline is 3, but the description adds a cross-parameter rule the schema does not express: `to` and `data` are alternatives, and omitting `to` while supplying `data` means contract creation. That is real semantic value beyond the per-field descriptions.

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 verb and resource ('Estimate the gas of a transaction') plus the exact chain scope, and immediately names the two nearest siblings it is not (get_gas for gas price, transfer_preflight for whole-transfer checks). An agent can distinguish it from those relatives without opening a schema.

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

Usage Guidelines5/5

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

Explicit routing guidance: use get_gas when only the gas price is wanted, use transfer_preflight for an end-to-end transfer check, and use this tool for the estimate itself. It also gives the selection rule between the two inputs ('send `to` or `data`'), so the agent knows when this tool applies and when to defer.

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.