Skip to main content
Glama

EVM & Solana Chain Reads (Tanod)

get_storage_at

Read-onlyIdempotent

chainpeek: Read a contract storage slot on Ethereum, Base or Robinhood Chain. For proxy implementation and admin slots use detect_proxy. Returns the 32-byte word at a storage slot of a contract (value), also as as_uint and, when it looks like an address, as_address, with is_zero; at latest, pending, finalized or a block number. 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.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>",
      "address": "<address>",
      "slot": "<slot>"
    },
    "name": "get_storage_at"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotYesStorage slot: 0x-hex up to 32 bytes, or a decimal number (0 is the first slot).
blockNolatest (default), pending, finalized or a block number.
chainYesethereum, base or robinhood (Robinhood Chain, chain id 4663).
addressYesContract address.

Output Schema

NameRequiredDescriptionDefault
slotNo
blockNo
chainNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
valueNo
addressNo
as_uintNo
is_zeroNo
as_addressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / address / title
      Removed value: -"Address"
    • 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 / slot / title
      Removed value: -"Slot"
    • removedInput schema / title
      Removed value: -"get_storage_atArguments"
  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.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: archive-node dependency and possible failure on old blocks, 30 s RPC read caching, 422 validation errors occurring before payment (not charged), sub-second latency, price and free-tier quota. This is exactly the behavioral detail annotations cannot carry.

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?

Dense but front-loaded: capability, chain scope and the sibling exclusion come first, then failure/caching/pricing notes. Some sentences duplicate what the output schema already defines (value/as_uint/as_address/is_zero) and the docs link plus price line are commercial boilerplate, but nothing is confusing.

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 simple four-parameter read, the description covers scope, alternative routing, failure conditions, caching freshness, cost model and latency, and an output schema exists to explain return values. An agent has everything needed to decide and invoke 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 coverage is 100%, so chain, address, slot and block are already fully documented with patterns and defaults. The description restates the accepted block tags and slot semantics but adds no new constraint or format detail beyond the schema; 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?

States a specific verb and resource ('Read a contract storage slot') plus the supported chains, and immediately names the sibling case it does not cover (proxy implementation/admin slots → detect_proxy). An agent can distinguish it from detect_proxy and the balance/code getters 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 Guidelines4/5

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

Explicitly routes proxy implementation and admin slot lookups to detect_proxy, and warns that old blocks require an archive node and may fail. It does not address other adjacent reads (e.g. contract code or balances), but the primary alternative and its selecting condition are stated.

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.