Skip to main content
Glama

Nansen

by io.github.nansen-ai
OverviewDiscussionsAdmin

Summarizing prediction market address

prediction_market_address_summary
Read-only

Prediction market summary metrics for a Polygon wallet.

When to use:

  • First wallet-level Polymarket tool for a quick trader overview.

  • Use before detailed address trades/PnL when the user asks for a general wallet profile, activity summary, or whether a wallet is active on Polymarket.

Key fields:

  • Markets Traded and Markets Won are lifetime counts; Win Rate is won / traded.

  • Total PnL USD = realized + unrealized.

  • First Seen and Wallet Age (Days) show how long the wallet has been active on Polymarket.

Pitfalls:

  • The API gives no trade count, volume, or ROI here. Do not state them. For per-market cost and proceeds use prediction_market_address_pnl.

  • 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: -{
-  "PredictionMarketAddressSummaryRequest": {
-    "description": "Request for address-level prediction market summary metrics.",
-    "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/PredictionMarketAddressSummaryRequest"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "Request for address-level prediction market summary metrics.",
+    "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.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses important behavioral details: lifetime vs. derived field semantics, Total PnL = realized + unrealized, and the critical caveat that blank PnL fields mean unavailable data, not zero. It also warns that trade count, volume, and ROI are not provided by this API.

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 organized with a one-line summary followed by concise, scannable sections for usage, key fields, and pitfalls. Every bullet earns its place and no redundant filler is present.

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?

This is complete for a read-only summary tool: it covers when to use it, what the lifetime metrics mean, what the API cannot provide, how to interpret missing values, and which sibling tool to fall back to. The output schema exists, so return-value details are already structured.

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 0%, so the description should compensate for missing parameter meaning, but it never explains the `request` object or how the address/page parameters work. It only says the tool is 'for a Polygon wallet,' which lightly hints at the address field but does not convey the request structure or pagination behavior.

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 identifies the tool as the wallet-level Polymarket summary, using 'Prediction market summary metrics for a Polygon wallet' and 'First wallet-level Polymarket tool for a quick trader overview.' It explicitly distinguishes itself from detailed trade/PnL tools, and the key-fields list grounds the purpose in concrete output semantics.

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 'When to use' section gives explicit conditions: use it before detailed address trades/PnL when the user wants a wallet profile, activity summary, or Polymarket activity check. It also names the sibling tool prediction_market_address_pnl as the alternative for per-market costs and proceeds.

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