Skip to main content
Glama

EmblemAI AgentWallet

nansen-wallets: nansen_wallet_counterparties

nansen_wallet_counterparties
Read-onlyIdempotent

Who a wallet or entity transacts with most: counterparties (wallets or entities) ranked by volume or interaction count, with in/out USD. Reveals exchanges used, funding sources and linked wallets. 5 credits.

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_counterparties"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days ending now (default 90). 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 20)
date_toNoExplicit end (YYYY-MM-DD or ISO 8601). Defaults to now.
sort_byNo
group_byNoGroup counterparties by wallet or by entity (default wallet)
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.
sort_directionNoSort direction (default DESC)
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 declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds the cost signal ('5 credits'), which is exactly the kind of operational context annotations cannot carry. It does not mention anything about pagination behavior or the cost scaling with limit/page, so it is not fully complete.

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 clauses: what it returns, what it reveals, and the credit cost. The core resource is front-loaded and every sentence carries unique information with no repetition.

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 an 11-parameter read-only query tool with high schema coverage and no output schema, the description covers purpose, output dimensions, insight value, and cost. The main gap is that it does not clarify wallet_address vs entity_name usage or the multi-chain re-query nuance (robinhood for 0x addresses), though those live in the schema.

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 91%, so parameters such as days, date_from/date_to, chain, group_by, and entity_name are already documented with defaults and interactions (entity_name points to nansen_search). The description adds no parameter-level meaning beyond the schema, which is acceptable at this coverage level.

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 states a specific verb and resource: counterparties of a wallet or entity ranked by volume or interaction count, with in/out USD, plus what that reveals (exchanges used, funding sources). An agent can tell this is a counterparty-ranking tool rather than a balances or PnL tool. It stops short of explicitly distinguishing itself from the closely named sibling nansen_wallet_related_wallets, which the phrase 'linked wallets' could even blur.

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 by the purpose statement — an agent can infer this is for identifying who a wallet interacts with most. There is no explicit when-to-use, when-not-to-use, or named alternative such as nansen_wallet_related_wallets for linked-wallet discovery or nansen_wallet_transactions for individual transfers.

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