Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

ws_subscribe_trades

Subscribe to real-time Polymarket trade updates via WebSocket and collect trades for a specified duration to monitor asset activity.

Instructions

Subscribe to real-time trade updates for Polymarket assets via WebSocket. Collects trades for specified duration.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "assetIds": "<assetIds>"
    },
    "name": "ws_subscribe_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdsYesArray of token/asset IDs to subscribe to (required). Get these from market clobTokenIds field.
durationSecondsNoHow long to collect trade updates in seconds (default: 10, max: 60)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the call is time-bounded ('collects trades for specified duration') rather than an indefinite stream, which is real value beyond the schema default. But it omits whether authentication is needed, rate limits, and what the collected result looks like, leaving meaningful gaps for a WebSocket tool.

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?

Two tight sentences with the mechanism and the scope front-loaded and no wasted wording. Nothing is repeated or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter subscription tool with no output schema and no annotations, the definition covers what the tool does and that collection is duration-bounded. It does not describe the shape of the returned trades or how the subscription terminates, which an agent needs to interpret results correctly.

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 coverage is 100% and both parameters are documented in the schema, including the default and max for durationSeconds and where to source assetIds. The description adds only the loose restatement 'for specified duration', so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: subscribe to real-time trade updates for Polymarket assets via WebSocket. The word 'trades' implicitly separates it from ws_subscribe_prices, but the description never names the sibling explicitly, so the differentiation relies on the caller reading the tool names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Collects trades for specified duration' implies a bounded polling-style collection rather than a persistent stream, which is useful context. However, it gives no explicit guidance on when to choose this over ws_subscribe_prices or the REST-based get_trades_by_wallet, and no prerequisites or exclusions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.