Skip to main content
Glama

Nansen Smart Money Netflow

nansen_smart_money_netflow
Read-onlyIdempotent

What is smart money buying or selling (net flow) on chain X, returns tokens ranked by net USD flow from Nansen "Smart Money" wallets (top traders + funds) over a time window. Positive = accumulation, negative = distribution. Example: nansen_smart_money_netflow({ chain: "ethereum", timeframe: "1d", _apiKey: "your-nansen-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain": "ethereum",
      "_apiKey": "your-nansen-api-key",
      "timeframe": "1d"
    },
    "name": "nansen_smart_money_netflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain to query (default "ethereum"), e.g. "ethereum", "solana", "base", "arbitrum".
limitNoMax tokens to return (default 20, max 50).
_apiKeyYesNansen API key from your nansen.ai account (paid, $10/10k credits PAYG).
timeframeNoNet-flow window to rank/surface: "1h", "1d" (=24h), "7d", or "30d". Default "1d".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Nansen API key from your nansen.ai account (paid — $10/10k credits PAYG)."New value: +"Nansen API key from your nansen.ai account (paid, $10/10k credits PAYG)."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, open-world call, and the description adds genuinely useful behavioral context beyond them: the sign convention (positive = accumulation, negative = distribution), the definition of 'Smart Money' as top traders plus funds, and the ranking basis (net USD flow). It stops short of noting credit cost or rate limits, though the API key cost is covered in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core behavior and sign convention come first in one dense sentence, with an example appended. The example invocation is largely redundant with the schema's own examples array, which is the only real waste.

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?

With no output schema, the description carries the burden of describing returns and does so adequately: token ranking by net USD flow, with sign semantics. Minor gaps remain around result shape (per-token fields) and pagination, but nothing that would prevent a correct call.

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 100%, so chain, limit, timeframe, and _apiKey are all documented structurally; the description only reinforces that results are ranked 'over a time window'. It adds no new meaning about parameter interactions or defaults beyond the schema, so the baseline 3 applies.

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 metric: tokens ranked by net USD flow from Nansen 'Smart Money' wallets over a time window, with sign convention explained. It is clearly distinct from nansen_smart_money_holdings (a snapshot of holdings vs. a flow ranking), though it does not name that sibling 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?

The framing question 'What is smart money buying or selling' implies the use case (detecting accumulation/distribution), but there is no explicit when-to-use/when-not guidance and no routing to sibling tools such as nansen_smart_money_holdings or nansen_wallet_profiler.

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.