polymarket-mcp-server

Overview Schema Source Related Servers Discussions Admin

X-ray a Polymarket market

polymarket_xray

Read-onlyIdempotent

Get a single-call snapshot of one Polymarket market: detail, executable quote, top holders, price history, and recent trades bundled into one report.

Instructions

The one-shot deep look at a market: detail + executable quote + whales + recent price history + recent trade tape, all in one call (several API calls bundled). Identify by token_id OR slug + outcome.

Args:

token_id (string, optional) OR slug (string) + outcome (string).
history_interval ('1h'|'6h'|'1d'|'1w'|'1m'|'max'): default '1d'.
trade_limit (1-50, default 10), holder_limit (1-20, default 5).

Returns: { tokenId, outcome, slug, question, detail, quote, whales, history, tape } (sections null-tolerant).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No	Market slug — alternative to token_id. Combine with 'outcome'.
`outcome`	No	Outcome name to select when using 'slug' (e.g. 'Yes' or 'No'). Defaults to the first outcome.
`token_id`	No	CLOB token id (the ~77-digit id for ONE outcome). Preferred when you already have it.
`trade_limit`	No	Recent trades to include (default 10).
`holder_limit`	No	Top holders per outcome (default 5).
`response_format`	No	Output format: 'markdown' (concise, human-readable; default) or 'json' (full structured data).	markdown
`history_interval`	No	Price-history window (default 1d).	1d

Output Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes
`tape`	Yes
`quote`	Yes
`detail`	Yes
`whales`	Yes
`history`	Yes
`outcome`	Yes
`tokenId`	Yes
`question`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld, non-destructive). The description adds meaningful behavioral context: sections are 'null-tolerant', the call bundles several API calls, and defaults are declared. This goes beyond what annotations provide.

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?

Front-loaded with the core purpose, then structured Args/Returns. Efficient, though it partially duplicates the schema's own parameter listing.

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 still summarizes the return shape and notes null tolerance. Combined with the Args block and annotations, the agent has everything needed to invoke 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 description coverage is 100% and the schema documents all 7 parameters including enums and ranges. The description restates defaults and the token_id/slug+outcome relationship but adds little beyond the schema. 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?

States a specific verb ('one-shot deep look') and resource ('a market'), and enumerates exactly what it bundles: detail, quote, whales, history, tape. This clearly distinguishes it from the sibling atomic tools like polymarket_get_market or polymarket_get_quote—it's the composite call.

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

Usage Guidelines4/5

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

Names the composite nature ('several API calls bundled') and the two identification paths (token_id OR slug+outcome), which implicitly tells the agent when to prefer it over single-purpose siblings. It doesn't explicitly say 'use this instead of calling the individual tools', so 4 rather than 5.

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