Nansen

by io.github.nansen-ai

Overview Discussions Admin

Checking prediction market PnL leaders

prediction_market_pnl_leaderboard

Read-only

PnL leaderboard for a Polymarket market.

When to use:

Only for profitability claims.

Key fields:

Total PnL USD = redemption + unrealized value + sell proceeds − buy cost, for this market only.
Net Buy Cost USD is what the wallet paid for shares.
Net Sell Proceeds USD is what it received for shares sold before resolution.
Redemption Value USD is the payout collected after the market settled.
Unrealized Value USD is the marked value of shares still held.
Side Held reflects current side exposure where the API provides it.

Pitfalls:

The API gives no ROI, volume, or trade count here. Do not state them.
If PnL fields are blank, say profitability is unavailable — do not substitute top holders or position size.

Prerequisites: If marketId is unknown, call prediction_market_lookup first.

Input Schema

Name	Required	Description	Default
`request`	Yes	Request for market-level PnL leaderboard.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

addedInput schema / properties / request / additionalProperties
```
Added value: +false
```

removedInput schema / properties / request / anyOf

Removed value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "description": "Request for market-level PnL leaderboard.",
-    "properties": {
-      "marketId": {
-        "description": "Numeric Polymarket market ID (e.g. '654412'). Obtain this from the prediction_market_screener tool.",
-        "maxLength": 100,
-        "minLength": 1,
-        "type": "string"
-      },
-      "page": {
-        "default": 1,
-        "description": "Page number for paginated results.",
-        "minimum": 1,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "marketId"
-    ],
-    "type": "object"
-  }
-]

addedInput schema / properties / request / description

Added value: +"Request for market-level PnL leaderboard."

addedInput schema / properties / request / properties

Added value: +{
+  "marketId": {
+    "description": "Numeric Polymarket market ID (e.g. '654412'). Obtain this from the prediction_market_screener tool.",
+    "maxLength": 100,
+    "minLength": 1,
+    "type": "string"
+  },
+  "page": {
+    "default": 1,
+    "description": "Page number for paginated results.",
+    "minimum": 1,
+    "type": "integer"
+  }
+}

addedInput schema / properties / request / required
```
Added value: +[
+  "marketId"
+]
```
addedInput schema / properties / request / type
```
Added value: +"object"
```

Changed3 schema fields changedMay 19, 2026

removedInput schema / $defs

Removed value: -{
-  "PredictionMarketPnlLeaderboardRequest": {
-    "description": "Request for market-level PnL leaderboard.",
-    "properties": {
-      "marketId": {
-        "description": "Numeric Polymarket market ID (e.g. '654412'). Obtain this from the prediction_market_screener tool.",
-        "maxLength": 100,
-        "minLength": 1,
-        "type": "string"
-      },
-      "page": {
-        "default": 1,
-        "description": "Page number for paginated results.",
-        "minimum": 1,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "marketId"
-    ],
-    "type": "object"
-  }
-}

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / request / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "$ref": "#/$defs/PredictionMarketPnlLeaderboardRequest"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "Request for market-level PnL leaderboard.",
+    "properties": {
+      "marketId": {
+        "description": "Numeric Polymarket market ID (e.g. '654412'). Obtain this from the prediction_market_screener tool.",
+        "maxLength": 100,
+        "minLength": 1,
+        "type": "string"
+      },
+      "page": {
+        "default": 1,
+        "description": "Page number for paginated results.",
+        "minimum": 1,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "marketId"
+    ],
+    "type": "object"
+  }
+]

AddedMar 25, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover read-only/open-world safety, while the description adds substantive behavior: how Total PnL is composed, which metrics the API lacks, and what to do when PnL fields are blank. Those are operational constraints beyond what annotations provide.

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 front-loaded with purpose and organized into 'When to use', 'Key fields', 'Pitfalls', and 'Prerequisites'. The field definitions and pitfalls are relevant to correct interpretation, and there is no obvious filler despite the Key fields block being the longest section.

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 simple read-only tool with a documented schema and output schema, the description supplies purpose, usage constraints, field semantics, and failure handling. The notable gap is the inconsistent marketId prerequisite, which leaves sourcing guidance ambiguous.

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?

With 100% schema description coverage, the schema already documents marketId and page, so the baseline is 3. The description adds a prerequisite, but it conflicts with the schema's note that marketId comes from prediction_market_screener by directing agents to prediction_market_lookup instead; that inconsistency prevents credit above baseline.

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 opening sentence names the specific verb/resource and scope ('PnL leaderboard for a Polymarket market'), and the 'Only for profitability claims' line plus pitfalls distinguish it from holder/position tools. An agent can tell this is market-level PnL, not address-level or top-holder 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?

It provides a clear when-to-use rule ('Only for profitability claims') and explicit exclusions ('do not substitute top holders or position size'), plus a prerequisite for resolving marketId. It stops short of naming the relevant alternative sibling for other PnL scopes, so it is not a full when/when-not/alternatives statement.

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?