Skip to main content
Glama

Nansen

by io.github.nansen-ai
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

TableJSON Schema
NameRequiredDescriptionDefault
requestYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+  }
+]
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses important behavioral nuances: 'The API gives no ROI or share count here. Do not state them.' and 'Blank PnL fields mean unavailable data, not zero.' These prevent the agent from making false inferences and add real value beyond the structured annotations.

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 well-structured with clear headings ('When to use', 'Key fields', 'Pitfalls') and front-loaded purpose. Every sentence adds meaningful information, and the format makes it easy to scan. It is detailed without being verbose.

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?

The description covers the key output fields, usage context, and common pitfalls. It does not explain the request parameter, but the schema provides details for the nested properties, and the output schema is present. Minor gaps like explicit pagination behavior are not covered, but the overall guidance is solid for a read-only analysis tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain the 'request' parameter structure at all. Although the schema includes descriptions for the nested 'address' and 'page' properties, the schema coverage is reported as 0% (the top-level 'request' parameter has no description). The description also does not mention pagination or how to specify the wallet address, so the agent must infer this from the tool name and schema alone.

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: 'Prediction market PnL breakdown for a Polygon wallet, market by market.' It clearly distinguishes this tool from the sibling prediction_market_address_summary by focusing on per-market detail versus aggregate, so an agent can select the right one 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?

The description has a dedicated 'When to use' section and explicitly names the alternative: 'use prediction_market_address_summary for the aggregate.' It also gives guidance on summing rows for a wallet total, leaving no ambiguity about when this tool is appropriate.

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