Skip to main content
Glama

EmblemAI AgentWallet

nansen-wallets: nansen_wallet_balances

nansen_wallet_balances
Read-onlyIdempotent

Current token balances of a wallet or entity on one chain (ethereum, solana or robinhood), with USD values, spam filtered. 1 credit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nansen_wallet_balances"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (default 1)
chainNoethereum, solana or robinhood. Default: solana for base58 addresses, ethereum for 0x addresses. For a 0x wallet call again with robinhood to cover Robinhood Chain.
limitNoRows to return (1-100, default 30)
entity_nameNoInstead of an address, query a whole Nansen entity by exact name (e.g. 'Binance', 'Wintermute'). Find names with nansen_search.
token_symbolNo
min_value_usdNoHide dust below this value
wallet_addressNoWallet address (0x... for Ethereum/Robinhood, base58 for Solana)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's added value is the cost disclosure ('1 credit') and the result-shaping notes (USD values included, spam filtered out). It still says nothing about pagination behavior or response size, which matters for a list 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?

A single dense sentence with the core operation front-loaded and scope, output enrichment and cost appended in priority order. No filler, no restatement of the title.

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?

For a 7-parameter read-only tool with no output schema, the description covers what the payload contains and what it costs, which is the main missing context. The remaining gaps are the unconstrained token_symbol filter and the fact that no parameters are required, leaving the address-versus-entity choice unclear.

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 86%, so the schema already documents chain defaults, pagination, limits and min_value_usd. The description restates the chain set and mentions 'wallet or entity' but adds no semantics for the undocumented token_symbol parameter or for how wallet_address and entity_name interact.

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: current token balances of a wallet or entity on one chain, with named chains and the derived data (USD values, spam filtered). An agent can tell this apart from nansen_wallet_balance_history by the word 'current', but the description never names a sibling to contrast with.

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?

Usage is only implied through 'Current', which suggests a point-in-time snapshot rather than a historical series. There is no explicit when-to-use versus chain-specific siblings such as solanaBalances or baseGetBalances, and no statement of preconditions such as needing a wallet_address or entity_name.

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