Nansen

Tracking Smart Money DEX trades

smart_traders_and_funds_dex_trades

Read-only

Get individual (per wallet, per transaction) DEX trades made by smart traders and funds (EXCLUDES whales, large holders, influencers, etc.) across all chains (default is ['all']) or specific chain(s). Use this to see exactly which wallet bought or sold what; use smart_traders_and_funds_netflow for the aggregated view.

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 individual smart money DEX trades (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"
-      },
-      "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"
-      },
-      "orderBy": {
-        "anyOf": [
-          {
-            "enum": [
-              "block_timestamp",
-              "trade_value_usd",
-              "token_bought_amount",
-              "token_sold_amount"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Sort field. Pass an exact value above or None for default ('block_timestamp')."
-      },
-      "orderByDirection": {
-        "default": "DESC",
-        "description": "Sort direction: 'ASC' or 'DESC' (case-insensitive).",
-        "enum": [
-          "ASC",
-          "DESC",
-          "asc",
-          "desc"
-        ],
-        "type": "string"
-      },
-      "page": {
-        "default": 1,
-        "type": "integer"
-      },
-      "tokenBoughtSymbol": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Filter to trades that bought this token symbol"
-      },
-      "tokenSoldSymbol": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Filter to trades that sold this token symbol"
-      },
-      "tradeValueUsd": {
-        "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 trade value in USD"
-      },
-      "traderAddress": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Filter by trader address"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Request for individual smart money DEX trades (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"
+      },
+      "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"
+      },
+      "orderBy": {
+        "anyOf": [
+          {
+            "enum": [
+              "block_timestamp",
+              "trade_value_usd",
+              "token_bought_amount",
+              "token_sold_amount"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Sort field. Pass an exact value above or None for default ('block_timestamp')."
+      },
+      "orderByDirection": {
+        "default": "DESC",
+        "description": "Sort direction: 'ASC' or 'DESC' (case-insensitive).",
+        "enum": [
+          "ASC",
+          "DESC",
+          "asc",
+          "desc"
+        ],
+        "type": "string"
+      },
+      "page": {
+        "default": 1,
+        "type": "integer"
+      },
+      "tokenBoughtSymbol": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Filter to trades that bought this token symbol"
+      },
+      "tokenSoldSymbol": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Filter to trades that sold this token symbol"
+      },
+      "tradeValueUsd": {
+        "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 trade value in USD"
+      },
+      "traderAddress": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Filter by trader address"
+      }
+    },
+    "type": "object"
+  }
+]

AddedSep 6, 2026

TDQS

A4.3/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 the safety profile is covered. The description adds valuable behavioral context beyond that: the data is individual per-wallet/per-transaction, and the population explicitly excludes whales/large holders/influencers, which shapes 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 sentences with no filler. The first sentence front-loads the scope, exclusions, and chain default; the second points to the relevant sibling. Every word earns its place.

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?

For a read-only query tool with an output schema and safety annotations, the description covers the core semantics: granularity, population exclusions, chain scope, and the aggregated alternative. Nothing critical is missing for an agent to decide whether to call this tool.

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 prose adds little parameter-specific meaning beyond the default chain behavior; the heavy lifting is done by the schema, which documents each filter (chains, orderBy, tradeValueUsd, traderAddress, token symbols, includeSmartMoneyLabels). Although context reports 0% schema description coverage, the embedded schema clearly describes the nested filters, so a baseline of 3 is appropriate.

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?

States a specific verb and resource: get individual DEX trades made by smart traders and funds, per wallet and per transaction. It explicitly excludes whales/large holders/influencers and names the default chain behavior, which distinguishes it from sibling tools like netflow, perp_trades, and dcas.

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?

Provides a clear routing cue: use this for exactly which wallet bought/sold what, and use smart_traders_and_funds_netflow for the aggregated view. It does not explicitly address other sibling alternatives, but the tool name and descriptions of those siblings make the distinction fairly obvious.

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?