Skip to main content
Glama

EmblemAI AgentWallet

nansen: nansen_token_transfers

nansen_token_transfers
Read-onlyIdempotent

Large token transfers with from/to addresses and labels (exchange deposits/withdrawals, whale moves). Filter by CEX/DEX/non-exchange and minimum USD value. 1 credit.

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": {
      "chain": "<chain>",
      "token_address": "<token_address>"
    },
    "name": "nansen_token_transfers"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days ending now (default 1). Ignored when date_from is set.
pageNoPage number for pagination (default 1)
chainYes
limitNoRows to return (1-100, default 20)
date_toNoExplicit end (YYYY-MM-DD or ISO 8601). Defaults to now.
sort_byNo
date_fromNoExplicit start (YYYY-MM-DD or ISO 8601). Overrides days.
include_cexNoInclude CEX transfers
include_dexNoInclude DEX transfers
min_value_usdNo
token_addressYesToken contract address (use nansen_search to resolve a symbol first)
sort_directionNoSort direction (default DESC)
smart_money_onlyNo
non_exchange_transfersNoInclude wallet-to-wallet transfers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds material context beyond that: the response shape (from/to addresses and labels, exchange vs. whale classification) and the cost ('1 credit'), which is the kind of rate/cost disclosure agents need before calling. It omits pagination behavior and any hard result caps.

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: capability and output content first, filtering second, cost last. No redundant restatement of the title or name, and every clause carries information an agent can act on.

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?

With 14 parameters, no output schema, and two undocumented parameters, the description does well to state the return shape and cost. But it leaves meaningful gaps: no word on pagination interaction with limit, no mention of per-chain differences for ethereum/solana, and no clarification of smart_money_only.

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 71%, so the baseline is 3, and the description only reinforces a subset of it — the exchange inclusion toggles and min_value_usd, plus the intent behind them (exchange deposits/withdrawals vs. wallet-to-wallet). It says nothing about smart_money_only or min_value_usd, both of which lack schema descriptions and remain ambiguous.

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 and verb: 'Large token transfers with from/to addresses and labels', and reserves a scope ('large', exchange deposits/withdrawals, whale moves) that separates it from aggregate flow or DEX-trade tools. It stops short of naming a sibling such as nansen_token_flows or nansen_token_dex_trades, so the boundary must be inferred from the scope words alone.

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?

'Filter by CEX/DEX/non-exchange and minimum USD value' implies the exploratory use case (finding whale or exchange moves) but never states when to choose this over the token_flows or dex_trades siblings. There are no exclusions or prerequisites, leaving routing to inference.

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