Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

ws_subscribe_prices

Subscribe to real-time Polymarket asset price updates over WebSocket and collect changes for a set duration to monitor live market movement.

Instructions

Subscribe to real-time price updates for Polymarket assets via WebSocket. Collects price changes 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_prices"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 the key non-obvious trait that this is a bounded collection window rather than an open-ended stream ('Collects price changes for specified duration'), but says nothing about what is returned, what happens at the 30s cap, or rate/auth limits.

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?

Two short sentences with the core action front-loaded and the duration behavior following immediately; nothing is padded. Slightly terse given the missing return-value context, but no wasted wording.

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 simple two-parameter streaming tool this covers the action and the time bound, but with no output schema the description should explain what a subscriber actually receives (a snapshot array? deltas? final result at expiry). That ambiguity matters for correct downstream use.

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%, including the default of 5 and max of 30 seconds and where to source assetIds (clobTokenIds). The description adds no parameter meaning beyond that, so the baseline of 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 price updates for Polymarket assets via WebSocket', plus a second sentence clarifying it collects price changes for a specified duration. This is clearly distinct from data-fetching siblings like get_live_volume, though it never explicitly contrasts itself with ws_subscribe_trades or ws_get_orderbook.

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?

Usage is only implied: an agent can infer this is for streaming price movement over a bounded window, but the description never says when to pick it over ws_subscribe_trades, ws_get_orderbook, or the REST price tools. No prerequisites, no exclusions, no alternative named.

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