Skip to main content
Glama

EmblemAI AgentWallet

nansen-wallets: nansen_wallet_balance_history

nansen_wallet_balance_history
Read-onlyIdempotent

Historical balance snapshots of a wallet or entity over a window, optionally for one token. Use to see when a wallet entered or exited a position. 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_balance_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days ending now (default 30). Ignored when date_from is set.
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)
date_toNoExplicit end (YYYY-MM-DD or ISO 8601). Defaults to now.
date_fromNoExplicit start (YYYY-MM-DD or ISO 8601). Overrides days.
entity_nameNoInstead of an address, query a whole Nansen entity by exact name (e.g. 'Binance', 'Wintermute'). Find names with nansen_search.
token_symbolNo
token_addressNo
wallet_addressNoWallet address (0x... for Ethereum/Robinhood, base58 for Solana)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds useful context the annotations lack: the 1-credit cost and the fact that results are a time series of snapshots rather than a single state. It does not disclose pagination behavior or the constraint that at least one of wallet_address/entity_name is effectively required (0 declared required params).

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?

Three short sentences, front-loaded with purpose, then use case, then cost. Nothing is padded and the credit note earns its place as a decision-relevant detail.

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

Completeness3/5

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

For a 10-parameter, zero-required tool with no output schema, the description should at least describe the shape of the returned snapshots (per-token balance rows over time) and note that paging via page/limit is needed for long windows. It omits return shape, pagination, and the address-or-entity requirement, leaving real gaps for a tool of this complexity.

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 80%, so the baseline is 3. The phrase "wallet or entity" hints at the wallet_address vs entity_name duality and "optionally for one token" signals token_symbol/token_address are optional filters, but neither adds syntax, precedence rules, or exclusivity beyond what the schema already documents.

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?

"Historical balance snapshots of a wallet or entity over a window, optionally for one token" gives a specific verb+resource plus scope (time window, optional token filter). This implicitly separates it from current-snapshot siblings like nansen_wallet_balances, but no sibling is named or contrasted 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?

"Use to see when a wallet entered or exited a position" supplies one concrete use case, which is more than nothing. However, it gives no when-not guidance and never routes the agent to nansen_wallet_balances (current balances) or nansen_wallet_pnl (P&L) for overlapping questions, so the agent must infer alternatives from names alone.

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