Skip to main content
Glama

Native balance, nonce and account type of an EVM address

evm_address
Read-only

Native balance, nonce and account type of an EVM address on Base (default), Ethereum, Arbitrum, Optimism or Polygon: a wallet, a contract, or an EIP-7702 delegated wallet with its delegate. On Ethereum also the ENS primary name, when it resolves back to the address. Read over public RPC. Related tools on this server, for a different need: evm_wallet when you need native balance and the major tokens of an EVM address; evm_balance when you need ERC-20 balance of an address for one token contract. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "address": "<address>"
    },
    "name": "evm_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobase (default), ethereum, arbitrum, optimism or polygon
addressYesEVM address, 0x…

Output Schema

NameRequiredDescriptionDefault
kindNo
chainNo
nonceNo
nativeNo
sourceNo
addressNo
checkedAtNo
codeBytesNo
disclaimerNo
delegatedToNo
primaryNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnly and openWorld; the description adds real behavioral context beyond them — reads happen over public RPC, cost is $0.002 per successful call via x402 in USDC on Base/Solana and other networks, and failed calls are not charged. The ENS-only-on-Ethereum caveat and the EIP-7702 delegate detail further describe what actually comes back.

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?

Purpose and chain scope are front-loaded, and the sibling routing plus pricing tail are each load-bearing. The middle section is a run-on chain of colons and semicolons that could be broken into shorter sentences, but nothing is redundant.

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 two-parameter read with an output schema, the description covers scope, chains, default, the special ENS/EIP-7702 cases, alternatives, and payment terms. Nothing an agent needs to call this correctly or anticipate cost 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 parameters are already documented and the baseline is 3. The description adds modest meaning: the chain parameter's default (Base) is reiterated in a usage context, and it clarifies that the address may be a wallet, contract, or delegated wallet, which affects how the returned account type should be read.

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 names a specific resource set (native balance, nonce, account type) scoped to one address across five named chains, and spells out what 'account type' means (wallet, contract, EIP-7702 delegate). It also names the two closest siblings and what they return instead, so an agent can separate it from evm_wallet and evm_balance 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 Guidelines5/5

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

Explicit routing is provided: use evm_wallet when you need balance plus major tokens, use evm_balance when you need a single ERC-20 balance. It also states the default chain (Base) and where the ENS extra applies (Ethereum only), so the agent knows both when to select this tool and how to configure it.

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.

Resources