Skip to main content
Glama

Nansen

by io.github.nansen-ai
OverviewDiscussionsAdmin

Analyzing recent activity

token_recent_flows_summary
Read-only

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
NameRequiredDescriptionDefault
requestYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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, 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"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Complete request for token recent flows summary (flattened).",
+    "properties": {
+      "chain": {
+        "default": "ethereum",
+        "description": "Blockchain network. Supported: arbitrum, arc, 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"
+  }
+]
  2. Changed1 schema field changed
    • 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"
+  }
+]
  3. Changed1 schema field changed
    • 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"
+  }
+]
  4. Changed3 schema fields changed
    • 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"
+  }
+]
  5. Changed1 schema field changed
    • 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"
  6. Changed4 schema fields changed
    • 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"
+]
  7. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds meaningful behavioral context: aggregation over lookback periods, the interpretation of positive/negative flow, exchange flow semantics, and perps mode return details. No contradiction with annotations.

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 detailed and well-structured with sections, but somewhat long. It front-loads the core purpose and uses bullets for return values, though some redundancy exists (e.g., repeated notes on positive/negative flow). Still, every major sentence adds value and it is not bloated to the point of distraction.

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, the description is remarkably complete: it covers scope, supported chains, return format, interpretation, limitations, modes, and proscriptions. With output schema present and annotations covering safety, nothing an agent needs to call it correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the burden. It explains modes (onchain_tokens vs perps), supported chains (ETH, SOL), lookback period options, and how mode defaults to perps for symbols. It also describes the request's flattened structure and return format, adding semantics far beyond the sparse 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 gets an on-chain flow snapshot across all wallet categories in one call, lists the segments, and explicitly contrasts with token_flows for specific date ranges. It is a specific verb+resource that distinguishes it from siblings.

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?

It provides explicit when-to-use guidance: correct for standard lookbacks like 1d, and explicitly names token_flows as the alternative for specific date ranges and hourly breakdowns. It also warns Bitcoin is not supported and instructs to use token_flows for granular needs, making selection unambiguous.

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

All Nansen toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources