Nansen

by io.github.nansen-ai

Overview Discussions Admin

Checking prediction market address trades

prediction_market_address_trades

Read-only

Prediction market trade history for a Polygon wallet.

Key fields:

Share Size is quantity traded in the displayed outcome side.
Value USD applies to that row only, not the whole transaction.

Pitfalls:

Use this for wallet trade activity, not profitability.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / request / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "description": "Request for address-level prediction market trades.",
-    "properties": {
-      "address": {
-        "description": "Polygon wallet address to analyze.",
-        "type": "string"
-      },
-      "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": "Optional date range for address trades. Defaults to the last 30 days."
-      },
-      "page": {
-        "default": 1,
-        "description": "Page number for paginated results.",
-        "minimum": 1,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "address"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "Request for address-level prediction market trades.",
+    "properties": {
+      "address": {
+        "description": "Polygon wallet address to analyze.",
+        "type": "string"
+      },
+      "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": "Optional date range for address trades. Defaults to the last 30 days."
+      },
+      "page": {
+        "default": 1,
+        "description": "Page number for paginated results.",
+        "minimum": 1,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "address"
+    ],
+    "type": "object"
+  }
+]

Changed3 schema fields changedMay 19, 2026

removedInput schema / $defs

Removed value: -{
-  "DateRange": {
-    "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"
-  },
-  "PredictionMarketAddressTradesRequest": {
-    "description": "Request for address-level prediction market trades.",
-    "properties": {
-      "address": {
-        "description": "Polygon wallet address to analyze.",
-        "type": "string"
-      },
-      "dateRange": {
-        "anyOf": [
-          {
-            "$ref": "#/$defs/DateRange"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional date range for address trades. Defaults to the last 30 days."
-      },
-      "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/PredictionMarketAddressTradesRequest"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "Request for address-level prediction market trades.",
+    "properties": {
+      "address": {
+        "description": "Polygon wallet address to analyze.",
+        "type": "string"
+      },
+      "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": "Optional date range for address trades. Defaults to the last 30 days."
+      },
+      "page": {
+        "default": 1,
+        "description": "Page number for paginated results.",
+        "minimum": 1,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "address"
+    ],
+    "type": "object"
+  }
+]

AddedMar 25, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only field-interpretation notes ('Share Size', 'Value USD') and a usage pitfall, without disclosing anything about freshness, pagination limits, or auth needs beyond the annotations.

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-loads the purpose and uses bolded headers with short bullets, so it is easy to scan. Slightly redundant since the explained fields live in the existing output schema, but the formatting earns its space.

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 and annotations covering safety, the description only needs purpose and routing, both of which it supplies. It is complete enough for correct selection, though it omits any clarification of the request object's confusing anyOf structure.

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?

Schema description coverage is reported at 0% for the sole top-level param, and the description never explains the request wrapper, its nested fields, or the ambiguous anyOf of an untyped object vs a typed one. Its field notes ('Share Size', 'Value USD') describe outputs, not inputs, so it fails to compensate for the parameter documentation gap.

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 verb+resource: 'Prediction market trade history for a Polygon wallet,' which tells an agent exactly what it retrieves and the chain scope. The Pitfalls line ('Use this for wallet trade activity, not profitability') actively distinguishes it from siblings like prediction_market_address_pnl and prediction_market_address_summary.

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?

Provides clear when-to-use guidance via the exclusion, contrasting 'wallet trade activity' against 'profitability,' which routes the agent away from the PnL sibling. It stops short of naming the specific alternative tool or stating prerequisites, so it is context-rich but not fully prescriptive.

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?