Tanod MCP server

chainpeek: estimate the gas of a transaction (eth_estimateGas) on Ethereum, Base or Robinhood Chain

estimate_gas

Read-onlyIdempotent

Estimate Ethereum, Base or Robinhood Chain transaction gas before sending. Returns the node's gas estimate plus a 20% buffer; nothing is signed or sent.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	Recipient. Omit with `data` to estimate a contract creation.
`data`	No	Calldata, 0x-hex with an even number of digits, at most 8 kB.
`from`	No	Sender (affects balance and allowance checks).
`chain`	Yes	ethereum, base or robinhood (Robinhood Chain, chain id 4663).
`value_wei`	No	Native value in wei, as a decimal or 0x-hex string.

Output Schema

TableJSON Schema

Name	Required	Description
`to`	No
`gas`	No
`from`	No
`note`	No
`chain`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`contract_creation`	No
`gas_with_20pct_buffer`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, but the description adds material context beyond them: nothing is signed or sent, reverting transactions return 422 and are not charged, invalid input 422s before payment, RPC reads cached up to 30 s, estimation is against latest block so real cost can differ, typical latency under 1 s.

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?

Front-loaded with purpose, then routing, then behavior, pricing and limits — every block is useful. It loses a point for redundancy: 'Nothing is signed or sent' appears twice and the chain list is restated in the closing sentence.

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?

An output schema exists so return values need not be explained, yet the description still names the returned fields (`gas`, `gas_with_20pct_buffer`). Error modes, pricing, free-tier limits, caching, latency and supported chains are all covered — complete for a paid RPC-read tool.

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 description coverage is 100%, so the schema baseline is 3, but the description adds genuine semantics beyond it: the `to`-or-`data` requirement, that omitting `to` with `data` estimates a contract creation, and that `from` affects balance and allowance checks.

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 (estimate gas) and resource (a transaction) plus the exact chains supported, and immediately distinguishes itself from `get_gas` (gas price) and `transfer_preflight` (whole transfer check). An agent can route without opening the 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?

Explicitly names the two alternatives and the condition that selects each: `get_gas` for price, `transfer_preflight` for a full transfer check. It also states the within-tool rule 'send `to` or `data`', so the agent knows when the call is valid.

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

Deploy Server