Skip to main content
Glama

Nansen

by io.github.nansen-ai
OverviewDiscussionsAdmin

Checking prediction market trades

prediction_market_trades
Read-only

Recent trades for a Polymarket market.

When to use:

  • Source of truth for recent fills and latest trade-tape pricing.

  • Do not overwrite recent trade prices with older OHLCV candles.

Key fields:

  • Share Size is quantity; Value USD is dollar value.

  • Each row is one visible trade leg — Value USD applies to that row, not the whole transaction hash.

Pitfalls:

  • Large visible trades do not by themselves identify smart money or institutions.

Prerequisites: If marketId is unknown, call prediction_market_lookup first.

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: -{
-  "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"
-  },
-  "PredictionMarketTradesRequest": {
-    "description": "Request for recent market trades.",
-    "properties": {
-      "dateRange": {
-        "anyOf": [
-          {
-            "$ref": "#/$defs/DateRange"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional date range for market trades. Defaults to the last 7 days."
-      },
-      "marketId": {
-        "description": "Numeric Polymarket market ID (e.g. '654412'). Obtain this from the prediction_market_screener tool.",
-        "maxLength": 100,
-        "minLength": 1,
-        "type": "string"
-      },
-      "page": {
-        "default": 1,
-        "description": "Page number for paginated results.",
-        "minimum": 1,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "marketId"
-    ],
-    "type": "object"
-  }
-}
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / request / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "$ref": "#/$defs/PredictionMarketTradesRequest"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "Request for recent market trades.",
+    "properties": {
+      "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 market trades. Defaults to the last 7 days."
+      },
+      "marketId": {
+        "description": "Numeric Polymarket market ID (e.g. '654412'). Obtain this from the prediction_market_screener tool.",
+        "maxLength": 100,
+        "minLength": 1,
+        "type": "string"
+      },
+      "page": {
+        "default": 1,
+        "description": "Page number for paginated results.",
+        "minimum": 1,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "marketId"
+    ],
+    "type": "object"
+  }
+]
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable behavioral context: each row is one trade leg with Value USD scoped to that row, and large visible trades do not indicate smart money. This clarifies return semantics and common misinterpretations beyond the structured metadata.

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 clear sections (When to use, Key fields, Pitfalls, Prerequisites) and is appropriately sized. It front-loads the core purpose and efficiently conveys all necessary guidance without redundancy.

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?

Given that an output schema exists, the description correctly focuses on usage, pitfalls, and field meanings. It covers prerequisites, typical use cases, and potential misinterpretations, making it fully adequate for an agent to call the tool correctly. No critical information 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?

The input schema already provides descriptions for all parameters (marketId, page, dateRange), so baseline is 3. The description adds a hint about obtaining marketId via prediction_market_lookup, but does not elaborate on page or dateRange semantics beyond the schema. It does not significantly enhance parameter understanding, but it doesn't need to given the schema coverage.

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 states 'Recent trades for a Polymarket market' with a specific verb and resource, and distinguishes itself as the 'source of truth for recent fills and latest trade-tape pricing.' It differentiates from siblings like prediction_market_ohlcv by emphasizing the trade-tape nature.

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?

Explicit 'When to use' section with clear guidance: it is the source for recent fills and warns not to overwrite with OHLCV. Also provides a prerequisite to call prediction_market_lookup if marketId is unknown, and a pitfall about interpreting large trades. This fully guides an agent on when and when not to use the tool.

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