Nansen

Analyzing recent activity

token_recent_flows_summary

Get an on-chain flow snapshot across ALL wallet categories in one call. This tool supports native ETH on Ethereum and native SOL on Solana, and is the correct choice for standard lookbacks such as 1d.

Returns TOTAL token flows per segment: 1. Public Figures 2. Top PnL Traders 3. Whales 4. Smart Traders 5. Exchanges 6. Fresh Wallets

Inflow and outflow of tokens between the segments is CRITICAL in identifying token price trends.

The values provided are aggregated over the specific lookback period (last 5min, 1d, 7d etc) specified. If you have SPECIFIC date ranges in mind, use token_flows instead.

NOTE Use token_flows for more granular data as it can filter between exact dates and provides HOURLY breakdowns.

Returns: Categorized token flow analysis as markdown.

For each segment, returns:
- Flow amount in USD
- Ratio compared to average flow
- Number of wallets

Format: "{Segment} wallet flow of {amount} ({ratio}x average, from {count} wallets)"

Notes: - Positive flow = net buying, negative flow = net selling - For Exchange Flow, positive means more inflow to exchanges, negative means more outflow from exchanges - Categorizes market participants by their historical behavior and characteristics

NOTE: Bitcoin is not supported. DO NOT use this tool for bitcoin.

Modes:

onchain_tokens (default): On-chain token flow intelligence across cohorts
perps: Hyperliquid perpetual futures — returns position intelligence (current aggregate long/short/total USD by cohort: Smart Money, Whales, Public Figures). Native tokens (SOL, ETH, BTC etc) are fully supported in perps mode.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJul 18, 2026

changedInput schema / properties / request / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "description": "Complete request for token recent flows summary (flattened).",
-    "properties": {
-      "chain": {
-        "default": "ethereum",
-        "description": "Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
-        "type": "string"
-      },
-      "lookbackPeriod": {
-        "default": "1d",
-        "description": "Lookback period for analysis",
-        "enum": [
-          "5m",
-          "1h",
-          "6h",
-          "12h",
-          "1d",
-          "7d"
-        ],
-        "type": "string"
-      },
-      "mode": {
-        "default": "onchain_tokens",
-        "description": "Analysis mode: 'onchain_tokens' for on-chain tokens, 'perps' for Hyperliquid perpetual futures by symbol. If mode is omitted and token_address is a symbol (not a contract address), mode defaults to 'perps'.",
-        "enum": [
-          "onchain_tokens",
-          "perps"
-        ],
-        "type": "string"
-      },
-      "tokenAddress": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "tokenAddress"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Complete request for token recent flows summary (flattened).",
+    "properties": {
+      "chain": {
+        "default": "ethereum",
+        "description": "Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, robinhood, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
+        "type": "string"
+      },
+      "lookbackPeriod": {
+        "default": "1d",
+        "description": "Lookback period for analysis",
+        "enum": [
+          "5m",
+          "1h",
+          "6h",
+          "12h",
+          "1d",
+          "7d"
+        ],
+        "type": "string"
+      },
+      "mode": {
+        "default": "onchain_tokens",
+        "description": "Analysis mode: 'onchain_tokens' for on-chain tokens, 'perps' for Hyperliquid perpetual futures by symbol. If mode is omitted and token_address is a symbol (not a contract address), mode defaults to 'perps'.",
+        "enum": [
+          "onchain_tokens",
+          "perps"
+        ],
+        "type": "string"
+      },
+      "tokenAddress": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "tokenAddress"
+    ],
+    "type": "object"
+  }
+]

Changed1 schema field changedJun 12, 2026

changedInput schema / properties / request / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "description": "Complete request for token recent flows summary (flattened).",
-    "properties": {
-      "chain": {
-        "default": "ethereum",
-        "description": "Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
-        "type": "string"
-      },
-      "lookbackPeriod": {
-        "default": "1d",
-        "description": "Lookback period for analysis",
-        "enum": [
-          "5m",
-          "1h",
-          "6h",
-          "12h",
-          "1d",
-          "7d"
-        ],
-        "type": "string"
-      },
-      "mode": {
-        "default": "onchain_tokens",
-        "description": "Analysis mode: 'onchain_tokens' for on-chain tokens, 'perps' for Hyperliquid perpetual futures by symbol",
-        "enum": [
-          "onchain_tokens",
-          "perps"
-        ],
-        "type": "string"
-      },
-      "tokenAddress": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "tokenAddress"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Complete request for token recent flows summary (flattened).",
+    "properties": {
+      "chain": {
+        "default": "ethereum",
+        "description": "Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
+        "type": "string"
+      },
+      "lookbackPeriod": {
+        "default": "1d",
+        "description": "Lookback period for analysis",
+        "enum": [
+          "5m",
+          "1h",
+          "6h",
+          "12h",
+          "1d",
+          "7d"
+        ],
+        "type": "string"
+      },
+      "mode": {
+        "default": "onchain_tokens",
+        "description": "Analysis mode: 'onchain_tokens' for on-chain tokens, 'perps' for Hyperliquid perpetual futures by symbol. If mode is omitted and token_address is a symbol (not a contract address), mode defaults to 'perps'.",
+        "enum": [
+          "onchain_tokens",
+          "perps"
+        ],
+        "type": "string"
+      },
+      "tokenAddress": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "tokenAddress"
+    ],
+    "type": "object"
+  }
+]

Changed3 schema fields changedMay 19, 2026

removedInput schema / $defs

Removed value: -{
-  "LookbackPeriod": {
-    "description": "Lookback periods for time-based analysis.",
-    "enum": [
-      "5m",
-      "1h",
-      "6h",
-      "12h",
-      "1d",
-      "7d"
-    ],
-    "type": "string"
-  },
-  "TokenRecentFlowsSummaryRequest": {
-    "description": "Complete request for token recent flows summary (flattened).",
-    "properties": {
-      "chain": {
-        "default": "ethereum",
-        "description": "Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
-        "type": "string"
-      },
-      "lookbackPeriod": {
-        "$ref": "#/$defs/LookbackPeriod",
-        "default": "1d",
-        "description": "Lookback period for analysis"
-      },
-      "mode": {
-        "default": "onchain_tokens",
-        "description": "Analysis mode: 'onchain_tokens' for on-chain tokens, 'perps' for Hyperliquid perpetual futures by symbol",
-        "enum": [
-          "onchain_tokens",
-          "perps"
-        ],
-        "type": "string"
-      },
-      "tokenAddress": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "tokenAddress"
-    ],
-    "type": "object"
-  }
-}

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / request / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "$ref": "#/$defs/TokenRecentFlowsSummaryRequest"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Complete request for token recent flows summary (flattened).",
+    "properties": {
+      "chain": {
+        "default": "ethereum",
+        "description": "Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync",
+        "type": "string"
+      },
+      "lookbackPeriod": {
+        "default": "1d",
+        "description": "Lookback period for analysis",
+        "enum": [
+          "5m",
+          "1h",
+          "6h",
+          "12h",
+          "1d",
+          "7d"
+        ],
+        "type": "string"
+      },
+      "mode": {
+        "default": "onchain_tokens",
+        "description": "Analysis mode: 'onchain_tokens' for on-chain tokens, 'perps' for Hyperliquid perpetual futures by symbol",
+        "enum": [
+          "onchain_tokens",
+          "perps"
+        ],
+        "type": "string"
+      },
+      "tokenAddress": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "tokenAddress"
+    ],
+    "type": "object"
+  }
+]

Changed1 schema field changedMay 13, 2026

changedInput schema / $defs / TokenRecentFlowsSummaryRequest / properties / chain / description

Previous value: -"Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync"New value: +"Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, mantra, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync"

Changed4 schema fields changedApr 28, 2026

addedInput schema / $defs / TokenRecentFlowsSummaryRequest / properties / chain / default
```
Added value: +"ethereum"
```

addedInput schema / $defs / TokenRecentFlowsSummaryRequest / properties / chain / description

Added value: +"Blockchain network. Supported: arbitrum, avalanche, base, bnb, ethereum, hyperevm, injective, iotaevm, linea, mantle, monad, near, optimism, plasma, polygon, ronin, scroll, sei, solana, sonic, sui, ton, tron, unichain, zksync"

addedInput schema / $defs / TokenRecentFlowsSummaryRequest / properties / mode

Added value: +{
+  "default": "onchain_tokens",
+  "description": "Analysis mode: 'onchain_tokens' for on-chain tokens, 'perps' for Hyperliquid perpetual futures by symbol",
+  "enum": [
+    "onchain_tokens",
+    "perps"
+  ],
+  "type": "string"
+}

changedInput schema / $defs / TokenRecentFlowsSummaryRequest / required

Previous value: -[
-  "chain",
-  "tokenAddress"
-]New value: +[
+  "tokenAddress"
+]

First observedFeb 18, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description fully carries the burden of behavioral disclosure. It explains the meaning of flow signs ('Positive flow = net buying, negative flow = net selling'), special exchange flow semantics, aggregation over lookback periods, and the distinction between onchain_tokens and perps modes. This gives a comprehensive behavioral picture beyond just input/output.

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 description is well-structured with clear sections, bullets, and notes, making it easy to scan. It front-loads the core purpose and then covers details systematically. There is slight redundancy (token_flows alternative mentioned twice), preventing a perfect score, but every sentence is informative and earns its place for a tool with multiple modes.

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

Completeness5/5

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

Given the tool's complexity (two modes, multiple wallet categories, unsupported assets, sign conventions), the description thoroughly covers all necessary aspects. It explains output format, segment categories, lookback behavior, and warns about Bitcoin. The presence of an output schema and the detailed description together provide complete contextual understanding for an agent to invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema contains descriptions for mode, chain, and lookbackPeriod, the description adds crucial context: it explains that values are aggregated over the lookback period, introduces the two modes, and clarifies that native ETH and SOL are supported (while BTC is not). The description also notes that perps mode returns position intelligence, which is not obvious from the schema's enum. This adds meaningful meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get an on-chain flow snapshot across ALL wallet categories in one call.' It specifies a concrete verb and resource, and differentiates itself from sibling tool token_flows by noting it is 'the correct choice for standard lookbacks such as 1d.' This distinguishes it clearly from other flow- or transfer-related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage guidance is explicit and actionable. The description states when to use this tool ('standard lookbacks such as 1d') and when to use alternatives: 'If you have SPECIFIC date ranges in mind, use token_flows instead.' It also includes a strong exclusion: 'Bitcoin is not supported. DO NOT use this tool for bitcoin.' This provides clear decision boundaries against siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nansen tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation4/5

Most tools have clearly distinct purposes (address vs token vs prediction market vs transaction). Overlapping tools like token_discovery_screener and nansen_score_top_tokens, or address_counterparties and address_related_addresses, are explicitly disambiguated with detailed usage guidance. A few tools (token_flows vs token_recent_flows_summary) require careful reading but are still distinguishable.

Naming Consistency4/5

Tool names consistently use snake_case with resource prefixes (address_*, token_*, prediction_market_*). Minor deviations include general_search, growth_chain_rank, and nansen_score_top_tokens, and some names like smart_traders_and_funds_perp_trades are verbose but still follow the pattern.

Tool Count3/5

38 tools is a heavy surface, but it matches Nansen's broad domain covering address analytics, token intelligence, prediction markets, and Hyperliquid perps. The count is on the high end and may overwhelm agents, but each tool appears to serve a distinct function within a reasonably scoped analytics platform.

Completeness5/5

The tool surface is comprehensive: address lifecycle (portfolio, transactions, balances, counterparties, PnL), token analytics (price, OHLCV, indicators, flows, transfers, holders, discovery), prediction markets (lookup, orderbook, trades, top holders, PnL), and specialized features (smart money, chain rankings). No obvious dead ends or missing critical operations are apparent.

Resources

Need Help?