Skip to main content
Glama

Account or contract details

zenith_get_account
Read-only

Retrieves EVM account details for an address, including balance, nonce, contract verification and metadata, token holdings, and recent transactions.

Instructions

Balance, nonce, wallet vs contract, and for contracts: verified source, proxy implementation, ERC-20 metadata, and whether the address is a Gateway inbox. Also lists token holdings and recent transactions from the explorer.

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": "zenith_get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesEVM address (0x…)
recentTransactionsNo
includeTokenHoldingsNoLook up ERC-20 balances from the explorer's transfer index

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral content beyond that: it performs source verification, proxy-implementation detection, ERC-20 metadata resolution, and Gateway inbox detection, and it pulls holdings/transactions from an external explorer. It stops short of disclosing cost, latency, rate limits, or what happens for a plain EOA versus a contract.

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?

Two compact sentences with no filler, and the core identity data (balance, nonce, wallet vs contract) is listed first. The colon-scoped contract clause keeps the conditional fields grouped rather than sprawling. Slightly list-like rather than front-loaded with a verb, but efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 3 parameters and no output schema, the description correctly shouldered the return-value burden and enumerated the response contents in detail, including contract-specific extras. Remaining gaps are modest: response shape/ordering and the EOA-versus-contract branch are not spelled out.

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 67%, so the schema already carries most parameter meaning. The description implicitly maps 'lists token holdings and recent transactions' to includeTokenHoldings and recentTransactions, which is useful reinforcement. It does not explain limits such as the 0-25 cap on recentTransactions or what happens when includeTokenHoldings is false, so it adds little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates exactly what the tool returns for an address: balance, nonce, wallet-vs-contract distinction, verified source, proxy implementation, ERC-20 metadata, Gateway inbox status, plus token holdings and recent transactions. That makes the resource and scope unmistakable, though it is a noun-phrase field list rather than a verb-led statement of purpose. It does not explicitly separate itself from adjacent siblings like zenith_read_contract or zenith_get_transaction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternative tool is named. The agent must infer from the field list that this is the first-call lookup for an arbitrary address, and has to guess whether zenith_read_contract or zenith_get_transaction covers any overlapping need.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.