Skip to main content
Glama

EVM & Solana Chain Reads (Tanod)

get_account_nonce

Read-onlyIdempotent

chainpeek: Get an account's transaction count on Ethereum, Base or Robinhood Chain. For the next nonce with balance and gas checks use transfer_preflight; for the chain head use get_block_number. Returns the account's transaction count (nonce, and nonce_hex) at latest, pending (includes the node's mempool: the next nonce to send) or finalized, from eth_getTransactionCount. 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>"
    },
    "name": "get_account_nonce"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockNolatest (default), pending (counts the node's mempool: use it for the next nonce to send) or finalized.latest
chainYesethereum, base or robinhood (Robinhood Chain, chain id 4663).
addressYesAccount address (0x + 40 hex).

Output Schema

NameRequiredDescriptionDefault
noteNo
blockNo
chainNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
nonceNo
addressNo
nonce_hexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / address / title
      Removed value: -"Address"
    • removedInput schema / properties / block / title
      Removed value: -"Block"
    • removedInput schema / properties / chain / title
      Removed value: -"Chain"
    • removedInput schema / title
      Removed value: -"get_account_nonceArguments"
  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
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety bar is low; the description still adds real context: nothing is signed or sent, RPC reads cached up to 30 s, typical latency under 1 s, price and the 10-free-reads-per-IP free tier, and that invalid input is a 422 before payment. The only gap is whether the cache can return slightly stale nonces.

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-loads purpose, then alternatives, then behavior, pricing and docs; dense but ordered. Pricing, free-tier and URL boilerplate plus a slightly run-on clause about caching keep it from being maximally tight.

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 output schema exists, so return values need no explanation, and the description covers supported chains, block semantics, cost, caching, latency and error behavior for a simple three-parameter read. An agent has everything needed to call it correctly and know what it costs.

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% and the description largely restates the schema's own enum explanations for block and chain, adding only a small gloss that pending includes the node's mempool. That is at the baseline for fully documented parameters rather than meaningfully beyond them.

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 transaction count") plus the exact scope (Ethereum, Base, Robinhood Chain). It explicitly names the siblings it is not (transfer_preflight for next nonce with checks, get_block_number for chain head), so an agent can separate them without opening schemas.

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?

Gives explicit routing: "For the next nonce with balance and gas checks use transfer_preflight; for the chain head use get_block_number." It also states the supported chains and defines when each block parameter applies (pending = next nonce to send), leaving nothing to inference.

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.