Skip to main content
Glama

Nansen

by io.github.nansen-ai
OverviewDiscussionsAdmin

Ranking Smart Money by PnL

smart_traders_and_funds_pnl_leaderboard
Read-only

Rank smart trader and fund addresses (EXCLUDES whales, large holders, influencers, etc.) by realized, unrealized and total USD PnL over a 1/7/30/90/180 day window, with ROI, win rate and trade counts. Use this to find the best performing smart money wallets; use token_pnl_leaderboard for the best performers on one specific token.

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 the smart money PnL leaderboard (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": [
-              "total_pnl_usd",
-              "realized_pnl_usd",
-              "unrealized_pnl_usd",
-              "avg_trade_roi",
-              "roi_percent_unrealised",
-              "win_rate",
-              "n_trades",
-              "n_tokens"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Sort field. Pass an exact value above or None for default ('total_pnl_usd')."
-      },
-      "orderByDirection": {
-        "default": "DESC",
-        "description": "Sort direction: 'ASC' or 'DESC' (case-insensitive).",
-        "enum": [
-          "ASC",
-          "DESC",
-          "asc",
-          "desc"
-        ],
-        "type": "string"
-      },
-      "page": {
-        "default": 1,
-        "type": "integer"
-      },
-      "timeframe": {
-        "default": 7,
-        "description": "Lookback window in days. Allowed values: 1, 7, 30, 90, 180.",
-        "enum": [
-          1,
-          7,
-          30,
-          90,
-          180
-        ],
-        "type": "integer"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Request for the smart money PnL leaderboard (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": [
+              "total_pnl_usd",
+              "realized_pnl_usd",
+              "unrealized_pnl_usd",
+              "avg_trade_roi",
+              "roi_percent_unrealised",
+              "win_rate",
+              "n_trades",
+              "n_tokens"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Sort field. Pass an exact value above or None for default ('total_pnl_usd')."
+      },
+      "orderByDirection": {
+        "default": "DESC",
+        "description": "Sort direction: 'ASC' or 'DESC' (case-insensitive).",
+        "enum": [
+          "ASC",
+          "DESC",
+          "asc",
+          "desc"
+        ],
+        "type": "string"
+      },
+      "page": {
+        "default": 1,
+        "type": "integer"
+      },
+      "timeframe": {
+        "default": 7,
+        "description": "Lookback window in days. Allowed values: 1, 7, 30, 90, 180.",
+        "enum": [
+          1,
+          7,
+          30,
+          90,
+          180
+        ],
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  }
+]
  2. Added

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 the agent knows this is a safe read operation. The description adds behavioral context by specifying that it EXCLUDES whales and large holders, and details the PnL metrics and time windows (1/7/30/90/180 days). This goes beyond the annotations and helps the agent understand the exact scope of the leaderboard.

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?

The description is two sentences long, with the first sentence front-loading the core purpose and scope, and the second sentence providing usage guidance and an alternative. There is no fluff or redundancy, making it efficient for an agent to parse quickly.

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?

For a read-only leaderboard tool with a rich input schema and an output schema present, the description provides enough context for the agent to understand the core functionality and when to use it. It does not describe the output format, but that is covered by the output schema. The main gap is that it does not mention the available filters (chains, labels) explicitly, though the schema covers them.

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 description mentions 'realized, unrealized and total USD PnL' and '1/7/30/90/180 day window', which directly map to the orderBy and timeframe parameters in the schema. However, it does not explain chains, orderByDirection, includeSmartMoneyLabels, or pagination. Since the schema itself has detailed descriptions for these properties, the description adds partial meaning but does not fully compensate for the 0% schema description coverage from the description side.

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 ranks smart trader and fund addresses by PnL metrics, explicitly excludes whales/large holders/influencers, and names the specific sibling (token_pnl_leaderboard) for the alternative use case. This distinguishes it from the many sibling tools that focus on specific tokens or other smart-money data.

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 provides explicit guidance on when to use this tool ('to find the best performing smart money wallets') and when to use the alternative ('use token_pnl_leaderboard for the best performers on one specific token'). This covers the primary routing scenario, though it does not mention other relevant siblings like smart_traders_and_funds_dcas or perp trades.

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