Skip to main content
Glama

EVM & Solana Chain Reads (Tanod)

eth_call

Read-onlyIdempotent

chainpeek: Call a smart contract function read-only on Ethereum, Base or Robinhood Chain. For gas units use estimate_gas; for a raw storage slot use get_storage_at. Returns the raw ABI-encoded return data (result, result_bytes) of eth_call against to with your calldata at latest, pending, finalized or a block number; nothing is signed or sent. The result is not decoded (decode_calldata decodes calldata; the ABI is yours). A call that reverts is a 422 reverted (not charged); results over 32 kB are a 502. Old blocks need an archive node and may fail. 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>",
      "to": "<to>",
      "data": "<data>"
    },
    "name": "eth_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesContract (or account) to call.
dataYesABI-encoded calldata, 0x-hex with an even number of digits, at most 8 kB (4-byte selector + arguments; 0x18160ddd is totalSupply()).
blockNolatest (default), pending, finalized or a block number (older blocks need an archive node and may fail).
chainYesethereum, base or robinhood (Robinhood Chain, chain id 4663).

Output Schema

NameRequiredDescriptionDefault
toNo
noteNo
blockNo
chainNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
resultNo
is_emptyNo
selectorNo
result_bytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / block / default
      Removed value: -null
    • removedInput schema / properties / block / title
      Removed value: -"Block"
    • removedInput schema / properties / chain / title
      Removed value: -"Chain"
    • removedInput schema / properties / data / title
      Removed value: -"Data"
    • removedInput schema / properties / to / title
      Removed value: -"To"
    • removedInput schema / title
      Removed value: -"eth_callArguments"
  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.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint=false), the description discloses the return shape (raw ABI-encoded `result`, `result_bytes`), that nothing is signed or sent, revert semantics (422 `reverted`, not charged), the 32 kB response cap (502), archive-node requirements for old blocks, a 30 s cache, typical latency, and pricing/free-tier details. This is substantially more than the structured fields provide.

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?

The purpose and the sibling routing are front-loaded, which is good, but the text is padded with near-duplicates: 'nothing is signed or sent' appears twice, 'read-only' is asserted in both the first and second half, and the chain list is repeated. Several sentences could be merged without losing information.

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 4-parameter read call with a full output schema, the definition covers the remaining decision-relevant unknowns: error behavior, cost and free quota, caching, archive-node limits and supported chains. Nothing an agent needs to invoke it correctly is missing.

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%, so the schema already documents `to`, `data`, `block` and `chain` including patterns and defaults. The description restates the block tags and the calldata concept without adding format or syntactic detail beyond the schema; the only marginal addition is the decode_calldata pointer.

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 ('Call a smart contract function read-only') plus the supported chains, and explicitly names the siblings it is not: estimate_gas for gas units, get_storage_at for raw storage slots, decode_calldata for decoding. An agent can distinguish it from those tools 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 routing is given: 'For gas units use estimate_gas; for a raw storage slot use get_storage_at', and the decoding boundary is stated ('decode_calldata decodes calldata; the ABI is yours'). When-to-use and when-to-use-something-else are both covered, with no inference required.

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.