Skip to main content
Glama

Nansen

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

NameRequiredDescriptionDefault
requestYesRequest for address-level prediction market summary metrics.

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 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 / properties / request / description
      Added value: +"Request for address-level prediction market summary metrics."
    • 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: -{
-  "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"
+  }
+]
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description still adds real value: it defines what each reported field means (Win Rate = won/traded, Total PnL = realized + unrealized), flags what the API does NOT return (trade count, volume, ROI), and warns that blank PnL means unavailable, not zero. That last point is a genuine data-quality trap an agent would otherwise mishandle.

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?

Well structured and front-loaded: one-line purpose, then When to use, Key fields, Pitfalls in priority order. Slightly verbose in the Key fields bullets, but each carries non-obvious semantics rather than restating the schema.

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?

An output schema exists, yet the description goes further by interpreting the returned fields and their failure modes, which is what an agent needs to report results responsibly. Nothing material for correct selection or interpretation 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?

Schema description coverage is 100%, so the address and page fields are already documented in structured form, and nested request wrapping is explicit. The description contributes only the implicit constraint that the address is a Polygon wallet; it says nothing about the pagination parameter. Baseline 3 is appropriate.

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 line states a specific resource and scope: lifetime summary metrics for a Polygon (Polymarket) wallet. It explicitly frames itself as the entry-level wallet overview, which separates it from depth tools like prediction_market_address_pnl and prediction_market_address_trades.

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' block names the triggering conditions (general wallet profile, activity summary, is-this-wallet-active) and the ordering rule (call this first, before detailed trades/PnL). The Pitfalls section names the explicit alternative — prediction_market_address_pnl — for per-market cost and proceeds, so routing is unambiguous.

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