AgentWallet MCP Server

get_balance

Retrieve a wallet's native token balance on a specific chain, returned in raw units (wei or lamports) and human-readable format for quick verification.

Instructions

Get the native token balance for a wallet on a specific chain. Returns balance in both wei (or lamports for Solana) and human-readable format.

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": {
      "wallet_id": "<wallet_id>"
    },
    "name": "get_balance"
  }
}

Input Schema

Name	Required	Description	Default
`chain_id`	No	Chain ID to check (defaults to wallet's default chain)
`wallet_id`	Yes	Wallet ID

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.14.8Oct 27, 2026
- addedInput schema / properties / chain_id / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / chain_id / minimum
```
Added value: +-9007199254740991
```
- addedInput schema / properties / wallet_id / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / wallet_id / minimum
```
Added value: +-9007199254740991
```
First observedv1.7.3Mar 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden, and it does add useful return-shape context: values come back in both wei and lamports (for Solana) and human-readable form. It says nothing about read-only semantics, error behavior for unknown wallet/chain, RPC failure modes, or whether the balance is confirmed vs pending — meaningful gaps for a zero-annotation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero waste, and the core action is front-loaded before the return-format detail.

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 only two parameters and no output schema, the description covers the essential behavior and even compensates for the missing output schema by describing the returned units. Only permission/auth and failure-mode context is absent.

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 description coverage is 100%, so both wallet_id and chain_id (including its default-to-wallet-chain behavior) are already documented in the schema. The description adds only the notion of chain-specificity and the unit naming; baseline 3 applies since the schema does the heavy lifting.

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?

States a specific verb and resource ('Get the native token balance') plus the scoping dimension ('for a wallet on a specific chain'). The word 'native' implicitly separates it from the token-balance sibling get_token_balance, though it never names that sibling explicitly.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not guidance, and no routing to get_token_balance for ERC-20 balances or to get_wallet for metadata. Usage is only implied by the phrasing 'for a wallet on a specific chain' and the schema's default-chain note.

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