Skip to main content
Glama

EVM & Solana Chain Reads (Tanod)

get_erc1155_balance

Read-onlyIdempotent

chainpeek: Get an account's ERC-1155 token balance for a token id on Ethereum, Base or Robinhood Chain. For an ERC-721 owner use get_nft_owner. Returns balanceOf(account, id) of an ERC-1155 contract (balance, a raw integer string), with an ERC-165 check (is_erc1155) and the block read. A contract without balanceOf(address,uint256) is a 422 not_erc1155 (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.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>",
      "contract": "<contract>",
      "account": "<account>",
      "token_id": "<token_id>"
    },
    "name": "get_erc1155_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesethereum, base or robinhood (Robinhood Chain, chain id 4663).
accountYesHolder address.
contractYesERC-1155 contract address.
token_idYesToken id (uint256) as a decimal or 0x-hex string.

Output Schema

NameRequiredDescriptionDefault
blockNo
chainNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
accountNo
balanceNo
contractNo
token_idNo
is_erc1155No

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / account / title
      Removed value: -"Account"
    • removedInput schema / properties / chain / title
      Removed value: -"Chain"
    • removedInput schema / properties / contract / title
      Removed value: -"Contract"
    • removedInput schema / properties / token_id / title
      Removed value: -"Token Id"
    • removedInput schema / title
      Removed value: -"get_erc1155_balanceArguments"
  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?

Annotations already declare read-only, idempotent, non-destructive, but the description adds substantial context beyond them: the ERC-165 is_erc1155 check, the 422 not_erc1155 outcome for contracts lacking balanceOf(address,uint256), the fact that failures are not charged, a 30 s RPC cache, and sub-second expected latency. It also states pricing and the free tier, which matters for a paid endpoint.

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 core purpose and sibling routing are front-loaded, and pricing/error semantics follow in short clauses. It is dense — pricing, docs URL, cache window and latency all appear — but each clause carries operational value rather than 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?

An agent knows what it will get (raw balance string plus is_erc1155 and block), what errors mean and whether they cost money, what chains work, what the call costs, and which sibling handles the adjacent case. Nothing needed 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it ties contract to ERC-1155 with a balanceOf(address,uint256) requirement, confirms token_id is a uint256 selector for that call, and enumerates which chain values are valid. This goes beyond the schema's field-level descriptions.

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 ("Get an account's ERC-1155 token balance for a token id") and scopes it to three named chains. It explicitly distinguishes itself from the nearest sibling: "For an ERC-721 owner use get_nft_owner."

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?

Gives a clear routing rule to the ERC-721 sibling and enumerates supported chains, which effectively excludes all other networks. It does not point to an ERC-20 balance alternative for fungible tokens, so the alternative coverage is partial rather than complete.

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.