Nansen

Checking Smart Money netflows

smart_traders_and_funds_netflow

Read-only

Get aggregated (not per wallet) smart trader and fund (EXCLUDES whales, large holders, influencers, etc.) net USD flow per token over 1h/24h/7d/30d, per chain for all chains (default is ['all']) or specific chain(s). Use this for what smart money is buying or selling right now; use smart_traders_and_funds_token_balances for what they hold.

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.

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / request / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "description": "Request for smart money token netflow (v1 API) - flattened.",
-    "properties": {
-      "chains": {
-        "description": "Optional list of chains to include. If omitted, defaults to ['all'] (all supported chains). Use 'all' to query all supported chains. Supported chains: arbitrum, avalanche, base, bnb, ethereum, hyperevm, iotaevm, linea, mantle, monad, optimism, plasma, polygon, robinhood, sei, solana, sonic, all",
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "includeNativeTokens": {
-        "default": true,
-        "description": "Whether to include native tokens (ETH, SOL, etc.) in results",
-        "type": "boolean"
-      },
-      "includeSmartMoneyLabels": {
-        "anyOf": [
-          {
-            "items": {
-              "enum": [
-                "30D Smart Trader",
-                "90D Smart Trader",
-                "180D Smart Trader",
-                "All Time Smart Trader",
-                "Fund",
-                "Smart HL Perps Trader",
-                "Any Smart Money"
-              ],
-              "type": "string"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Smart money category filters to include"
-      },
-      "includeStablecoin": {
-        "default": true,
-        "description": "Whether to include stablecoins in results",
-        "type": "boolean"
-      },
-      "marketCapUsd": {
-        "anyOf": [
-          {
-            "description": "Numeric range where from_value and to_value are optional,\nallowing for open-ended ranges (e.g., only minimum or only maximum).",
-            "properties": {
-              "from": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "default": null,
-                "description": "Minimum value (inclusive), optional"
-              },
-              "to": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "default": null,
-                "description": "Maximum value (inclusive), optional"
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Filter by token market capitalisation in USD"
-      },
-      "orderBy": {
-        "anyOf": [
-          {
-            "enum": [
-              "net_flow_1h_usd",
-              "net_flow_24h_usd",
-              "net_flow_7d_usd",
-              "net_flow_30d_usd",
-              "trader_count",
-              "token_age_days",
-              "market_cap_usd"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Sort field. Pass an exact value above or None for default ('net_flow_24h_usd')."
-      },
-      "orderByDirection": {
-        "default": "DESC",
-        "description": "Sort direction: 'ASC' or 'DESC' (case-insensitive).",
-        "enum": [
-          "ASC",
-          "DESC",
-          "asc",
-          "desc"
-        ],
-        "type": "string"
-      },
-      "page": {
-        "default": 1,
-        "type": "integer"
-      },
-      "tokenAddress": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Restrict results to a single token address"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Request for smart money token netflow (v1 API) - flattened.",
+    "properties": {
+      "chains": {
+        "description": "Optional list of chains to include. If omitted, defaults to ['all'] (all supported chains). Use 'all' to query all supported chains. Supported chains: arbitrum, arc, avalanche, base, bnb, ethereum, hyperevm, iotaevm, linea, mantle, monad, optimism, plasma, polygon, robinhood, sei, solana, sonic, all",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "includeNativeTokens": {
+        "default": true,
+        "description": "Whether to include native tokens (ETH, SOL, etc.) in results",
+        "type": "boolean"
+      },
+      "includeSmartMoneyLabels": {
+        "anyOf": [
+          {
+            "items": {
+              "enum": [
+                "30D Smart Trader",
+                "90D Smart Trader",
+                "180D Smart Trader",
+                "All Time Smart Trader",
+                "Fund",
+                "Smart HL Perps Trader",
+                "Any Smart Money"
+              ],
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Smart money category filters to include"
+      },
+      "includeStablecoin": {
+        "default": true,
+        "description": "Whether to include stablecoins in results",
+        "type": "boolean"
+      },
+      "marketCapUsd": {
+        "anyOf": [
+          {
+            "description": "Numeric range where from_value and to_value are optional,\nallowing for open-ended ranges (e.g., only minimum or only maximum).",
+            "properties": {
+              "from": {
+                "anyOf": [
+                  {
+                    "type": "number"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "default": null,
+                "description": "Minimum value (inclusive), optional"
+              },
+              "to": {
+                "anyOf": [
+                  {
+                    "type": "number"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "default": null,
+                "description": "Maximum value (inclusive), optional"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Filter by token market capitalisation in USD"
+      },
+      "orderBy": {
+        "anyOf": [
+          {
+            "enum": [
+              "net_flow_1h_usd",
+              "net_flow_24h_usd",
+              "net_flow_7d_usd",
+              "net_flow_30d_usd",
+              "trader_count",
+              "token_age_days",
+              "market_cap_usd"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Sort field. Pass an exact value above or None for default ('net_flow_24h_usd')."
+      },
+      "orderByDirection": {
+        "default": "DESC",
+        "description": "Sort direction: 'ASC' or 'DESC' (case-insensitive).",
+        "enum": [
+          "ASC",
+          "DESC",
+          "asc",
+          "desc"
+        ],
+        "type": "string"
+      },
+      "page": {
+        "default": 1,
+        "type": "integer"
+      },
+      "tokenAddress": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Restrict results to a single token address"
+      }
+    },
+    "type": "object"
+  }
+]

AddedSep 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds meaningful behavioral context by clarifying that data is aggregated, not per-wallet, and that whales/large holders/influencers are excluded, which materially affects interpretation of results.

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?

Two crisp sentences front-load the core behavior and end with a pointer to the relevant sibling. No filler words, and every clause adds decision-relevant information.

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?

Given the read-only annotations and the presence of an output schema, the description is sufficient for an agent to select and invoke the tool correctly. It covers the key dimensions of aggregation, exclusions, timeframes, and chain scope, though it could marginally benefit from mentioning default ordering or filtering options explicitly.

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?

The top-level schema has 0% description coverage, so the description partially compensates by explaining the core semantics: USD net flow per token over 1h/24h/7d/30d and per-chain filtering with a default of all chains. However, it does not explain the required request wrapper or any of the filter options beyond chains, leaving the nested schema to carry most parameter-level meaning.

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 a specific verb ('Get') and resource ('aggregated smart trader and fund net USD flow per token'), and explicitly scopes what is included and excluded ('EXCLUDES whales, large holders, influencers, etc.'). It also differentiates itself from a sibling tool by pointing to smart_traders_and_funds_token_balances for holdings.

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

Usage Guidelines4/5

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

The description gives a clear usage context: use this for what smart money is buying or selling right now, and use smart_traders_and_funds_token_balances for what they hold. It names one key alternative but does not fully cover when to choose other smart-money siblings like dcas, dex_trades, or historical balances.

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

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

Need Help?