Skip to main content
Glama

Nansen

by io.github.hurcanNansen
OverviewDiscussionsAdmin

Checking prediction market address PnL

prediction_market_address_pnl
Read-only

Prediction market PnL breakdown for a Polygon wallet, market by market.

When to use:

  • Wallet-level Polymarket track record with per-market cost and proceeds.

Key fields:

  • Total PnL USD = redemption + unrealized value + sell proceeds − buy cost, for that 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.

  • Resolved says whether the market has settled.

Pitfalls:

  • Each row covers one market. Sum the rows for a wallet total, or use prediction_market_address_summary for the aggregate.

  • The API gives no ROI or share count here. Do not state them.

  • Blank PnL fields mean unavailable data, not zero.

Input Schema

NameRequiredDescriptionDefault
requestYesRequest for address-level prediction market PnL.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / request / additionalProperties
      Added value: +false
    • removedInput schema / properties / request / anyOf
      Removed value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "description": "Request for address-level prediction market PnL.",
-    "properties": {
-      "address": {
-        "description": "Polygon wallet address to analyze.",
-        "type": "string"
-      },
-      "page": {
-        "default": 1,
-        "description": "Page number for paginated results.",
-        "minimum": 1,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "address"
-    ],
-    "type": "object"
-  }
-]
    • addedInput schema / properties / request / description
      Added value: +"Request for address-level prediction market PnL."
    • addedInput schema / properties / request / properties
      Added value: +{
+  "address": {
+    "description": "Polygon wallet address to analyze.",
+    "type": "string"
+  },
+  "page": {
+    "default": 1,
+    "description": "Page number for paginated results.",
+    "minimum": 1,
+    "type": "integer"
+  }
+}
    • addedInput schema / properties / request / required
      Added value: +[
+  "address"
+]
    • addedInput schema / properties / request / type
      Added value: +"object"
  2. Changed3 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
-  "PredictionMarketAddressPnlRequest": {
-    "description": "Request for address-level prediction market PnL.",
-    "properties": {
-      "address": {
-        "description": "Polygon wallet address to analyze.",
-        "type": "string"
-      },
-      "page": {
-        "default": 1,
-        "description": "Page number for paginated results.",
-        "minimum": 1,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "address"
-    ],
-    "type": "object"
-  }
-}
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / request / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "$ref": "#/$defs/PredictionMarketAddressPnlRequest"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "Request for address-level prediction market PnL.",
+    "properties": {
+      "address": {
+        "description": "Polygon wallet address to analyze.",
+        "type": "string"
+      },
+      "page": {
+        "default": 1,
+        "description": "Page number for paginated results.",
+        "minimum": 1,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "address"
+    ],
+    "type": "object"
+  }
+]
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), yet the description still adds real behavioral context: each row is one market and must be summed, blank PnL fields mean unavailable rather than zero, and the API exposes no ROI or share count. It stops short of permissions, rate limits, or pagination behavior, but the data-shape caveats are exactly what prevents misreporting.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose followed by tight, labeled sections; every pitfall earns its place. The per-field definitions partly restate information an output schema already carries, so a little length is not strictly necessary, but the formula for Total PnL adds interpretive value.

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 per-market breakdown with an output schema present, the description covers the one thing the schema cannot: how rows aggregate into a wallet total and how to interpret blank values. Nothing needed to call or trust the result is missing.

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?

There is effectively one meaningful parameter (nested `request.address`, plus `page`), and the schema documents both at 100% coverage with a default for `page`. The description adds only that the address is a Polygon wallet, which is already implied by the purpose statement, so it does little beyond the schema — baseline 3.

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 resource and verb: a per-market PnL breakdown for a Polygon wallet. The Pitfalls section explicitly distinguishes it from the sibling `prediction_market_address_summary`, which returns the aggregate, so an agent can pick the right tool without opening either 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?

A dedicated "When to use" line gives the selecting condition (wallet-level Polymarket track record with per-market cost and proceeds), and the Pitfalls section names the alternative tool and the exact condition for switching to it (summing rows vs. the summary endpoint).

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