Skip to main content
Glama

EmblemAI AgentWallet

nansen-wallets: nansen_wallet_transactions

nansen_wallet_transactions
Read-onlyIdempotent

Recent transactions of a wallet or entity with tokens moved, counterparties (labelled) and USD volume. 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_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days ending now (default 7). 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.
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
min_volume_usdNo
sort_directionNoDESC = newest first (default)
wallet_addressNoWallet address (0x... for Ethereum/Robinhood, base58 for Solana)
counterparty_nameNoe.g. 'Binance'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the full safety profile (readOnly, non-destructive, idempotent, open-world), so the description's marginal burden is low. It adds the per-call cost ('1 credit') and a short preview of returned fields, which is genuine added value, but says nothing about pagination limits, empty results, or the dual-address/chain ambiguity the schema warns about.

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 front-loaded sentence with zero filler: what is returned, then the credit cost. Nothing is redundant or buried.

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 12-parameter, all-optional query tool with rich schema descriptions and full annotations, the description plus structured fields give an agent enough to call it correctly. The gaps left (no sibling routing, no mention of the entity_name address alternative) are covered in the schema text rather than the description.

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 83%, so parameter meaning is largely carried by the schema and the baseline of 3 applies. The description adds no parameter-level meaning, leaving undocumented fields (token_symbol, min_volume_usd, counterparty_name) without any narrative guidance.

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 names a specific resource (recent transactions of a wallet or entity) and previews the payload: tokens moved, labelled counterparties, USD volume. It is clearly distinct from balance or PnL siblings by implication, though it never names an alternative to contrast against.

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 named alternative (e.g. nansen_wallet_dex_trades or nansen_wallet_counterparties) for narrower queries. The only usage signal is the '1 credit' cost note, which is a cost hint rather than routing guidance.

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