Skip to main content
Glama

Nansen

by io.github.nansen-ai
OverviewDiscussionsAdmin

Reviewing Smart Money holdings history

smart_traders_and_funds_historical_token_balances
Read-only

Get the day-by-day history of aggregated smart trader and fund token balances (EXCLUDES whales, large holders, influencers, etc.) for a date range on base, bnb, ethereum, monad, robinhood or solana. Use this to see how smart money holdings changed over time; use smart_traders_and_funds_token_balances for the current snapshot.

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": "Request for smart money historical token balances (v1 API) - flattened.",
-    "properties": {
-      "chains": {
-        "description": "Chains to include. Supported: base, bnb, ethereum, monad, robinhood, solana.",
-        "items": {
-          "enum": [
-            "base",
-            "bnb",
-            "ethereum",
-            "monad",
-            "robinhood",
-            "solana"
-          ],
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "dateRange": {
-        "anyOf": [
-          {
-            "description": "Date range via tokens or dates.\nTokens: NOW, XMIN_AGO, XD_AGO, XH_AGO; THIS_YEAR_START, THIS_QUARTER_START, THIS_MONTH_START, THIS_WEEK_START, TODAY_START; LAST_WEEK_START/END, LAST_MONTH_START/END, LAST_QUARTER_START/END, LAST_YEAR_START/END.\nWeek starts Monday. Quarters are calendar. Dates: YYYY-MM-DD or ___-MM-DD (year omitted).\nPlease check detailed system instructions for more information.",
-            "properties": {
-              "from": {
-                "description": "Start value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
-                "type": "string"
-              },
-              "to": {
-                "description": "End value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
-                "type": "string"
-              }
-            },
-            "required": [
-              "from",
-              "to"
-            ],
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Date range for the history. Defaults to the last 30 days. Maximum lookback is 4 years."
-      },
-      "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"
-      },
-      "orderBy": {
-        "anyOf": [
-          {
-            "enum": [
-              "date",
-              "value_usd",
-              "balance",
-              "balance_24h_percent_change",
-              "holders_count",
-              "share_of_holdings_percent",
-              "market_cap_usd"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Sort field. Pass an exact value above or None for default ('date')."
-      },
-      "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 the history to a single token address"
-      },
-      "tokenSymbol": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Restrict the history to a single token symbol"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Request for smart money historical token balances (v1 API) - flattened.",
+    "properties": {
+      "chains": {
+        "description": "Chains to include. Supported: base, bnb, ethereum, monad, robinhood, solana.",
+        "items": {
+          "enum": [
+            "base",
+            "bnb",
+            "ethereum",
+            "monad",
+            "robinhood",
+            "solana"
+          ],
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "dateRange": {
+        "anyOf": [
+          {
+            "description": "Date range via tokens or dates.\nTokens: NOW, ALL_TIME, XMIN_AGO, XD_AGO, XH_AGO; THIS_YEAR_START, THIS_QUARTER_START, THIS_MONTH_START, THIS_WEEK_START, TODAY_START; LAST_WEEK_START/END, LAST_MONTH_START/END, LAST_QUARTER_START/END, LAST_YEAR_START/END.\nALL_TIME is full history. It resolves to 2009-01-03. Use ALL_TIME instead of a very large day count.\nWeek starts Monday. Quarters are calendar. Dates: YYYY-MM-DD or ___-MM-DD (year omitted).\nPlease check detailed system instructions for more information.",
+            "properties": {
+              "from": {
+                "description": "Start value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
+                "type": "string"
+              },
+              "to": {
+                "description": "End value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
+                "type": "string"
+              }
+            },
+            "required": [
+              "from",
+              "to"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Date range for the history. Defaults to the last 30 days. Maximum lookback is 4 years."
+      },
+      "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"
+      },
+      "orderBy": {
+        "anyOf": [
+          {
+            "enum": [
+              "date",
+              "value_usd",
+              "balance",
+              "balance_24h_percent_change",
+              "holders_count",
+              "share_of_holdings_percent",
+              "market_cap_usd"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Sort field. Pass an exact value above or None for default ('date')."
+      },
+      "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 the history to a single token address"
+      },
+      "tokenSymbol": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Restrict the history to a single token symbol"
+      }
+    },
+    "type": "object"
+  }
+]
  2. Added

TDQS

A4.4/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 genuinely useful behavioral context beyond the annotations: the exclusion of whales/large holders/influencers and the day-by-day aggregation granularity. It does not restate the 30-day default or 4-year lookback cap here (those live in the schema), but the entity-scoping caveat is a meaningful addition.

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, front-loaded with the core purpose and scope, then the routing hint to the sibling. Every clause earns its place with no padding.

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 an output schema present, return values need not be explained, and annotations cover safety. The description supplies purpose, scope exclusion, supported chains, and the snapshot alternative, which is close to complete for a read-only historical query. It stops short of noting pagination or the lookback ceiling in the description itself, but those exist in the schema.

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?

Reported schema description coverage is 0% at the top level, but the nested request schema in fact carries rich per-field descriptions (chains, dateRange tokens, orderBy, ordering direction, include* flags). The description reinforces the chain and date-range dimensions but adds little beyond what the nested schema already documents, so the 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?

The description states a specific verb and resource ('day-by-day history of aggregated smart trader and fund token balances'), scopes the entity set explicitly ('EXCLUDES whales, large holders, influencers, etc.'), lists supported chains, and names the sibling it differs from (smart_traders_and_funds_token_balances). An agent can distinguish it from related balance and history tools without opening the schema.

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 gives the selection condition directly: use this for how holdings 'changed over time' versus the current snapshot tool. The alternative is named and the deciding factor (time series vs. point-in-time) is explicit, leaving nothing to inference.

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