Tanod MCP server

chainpeek: chain id, latest block, head age and gas price of Ethereum, Base or Robinhood Chain

get_chain_info

Read-onlyIdempotent

Fetch chain ID, head block, block age, and gas price for Ethereum, Base, or Robinhood Chain to check network liveness and fees.

Instructions

chainpeek: Get the chain id, latest block, head age and gas price of Ethereum, Base or Robinhood Chain. For gas alone use get_gas; for the header alone use get_block. Returns chain_id, the latest block_number and block_timestamp, head_age_s (seconds since the head block, a liveness check), gas_price_gwei, base_fee_gwei, and the block's gas used and limit. Three RPC reads. 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.001. 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	Default
`chain`	Yes	ethereum, base or robinhood (Robinhood Chain, chain id 4663).

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`chain`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`chain_id`	No
`gas_used`	No
`gas_limit`	No
`head_age_s`	No
`block_number`	No
`base_fee_gwei`	No
`gas_price_wei`	No
`native_symbol`	No
`gas_price_gwei`	No
`block_timestamp`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations carry the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description layers on real operational detail beyond them: three RPC reads, 30 s caching, sub-1 s latency, 422 pre-payment validation with no charge on bad input, and 'nothing is signed or sent.'

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 alternatives then return fields then cost/limits, which is the right order. Slightly repetitive — the chain list appears in the title, the opening sentence, and again later ('Ethereum, Base and Robinhood only') — but no sentence is filler.

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 one-param read tool with an output schema, this covers purpose, alternatives, return shape, pricing, rate limits, caching, latency, and error/charge behavior. An agent has everything needed to decide and call correctly.

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 description coverage is 100% and the single `chain` enum is fully documented in the schema, including chain id 4663 for robinhood. The description restates the same chain list rather than adding format or default semantics, so baseline 3 applies.

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?

The description states a specific verb and resource (get chain id, latest block, head age, gas price) and explicitly differentiates from siblings: 'For gas alone use get_gas; for the header alone use get_block.' An agent can route correctly without opening any 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 when-to-use routing is given for both alternatives, plus chain eligibility ('Ethereum, Base and Robinhood only') and a free-tier/billing context (10 free reads per IP per UTC day, USD 0.001 after). Nothing is left to inference.

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

Deploy Server