Skip to main content
Glama

EVM & Solana Chain Reads (Tanod)

get_chain_info

Read-onlyIdempotent

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

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": "get_chain_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesethereum, base or robinhood (Robinhood Chain, chain id 4663).

Output Schema

NameRequiredDescriptionDefault
noteNo
chainNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
chain_idNo
gas_usedNo
gas_limitNo
head_age_sNo
block_numberNo
base_fee_gweiNo
gas_price_weiNo
native_symbolNo
gas_price_gweiNo
block_timestampNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / chain / title
      Removed value: -"Chain"
    • removedInput schema / title
      Removed value: -"get_chain_infoArguments"
  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.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that this performs three RPC reads, is read-only with nothing signed or sent, caches reads for up to 30 seconds, typically returns under 1 second, and has pricing/free-tier details. It also states that invalid inputs are rejected with 422 before payment, which is useful behavioral context.

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 front-loaded with purpose and alternatives, then gives return fields and operational details. It is mostly efficient, but the 422 note about bad addresses, hashes, hex strings, blocks or ranges is boilerplate that is not relevant to this tool's only parameter.

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?

Given the simple one-parameter interface, rich annotations, and existing output schema, the description is complete enough for correct invocation. It covers supported chains, read-only behavior, caching, latency, payment details, and documentation.

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% for the single required chain parameter, and the schema already documents the enum and chain ID. The description repeats the supported chain names but adds no additional parameter semantics beyond the schema.

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 gives a specific verb and resource: get the chain id, latest block, head age and gas price for named chains. It also distinguishes this tool from siblings by explicitly saying to use get_gas for gas alone and get_block for the header alone.

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?

It explicitly names alternatives and the conditions that select them: get_gas for gas alone, get_block for the header alone. The supported chain set is also stated, so the agent knows when this tool applies.

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.