polymarket-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| top_marketsC | Top Polymarket markets by 24h volume |
| search_marketsC | Search Polymarket markets by keyword |
| get_marketC | Get detailed info about a specific Polymarket market by slug |
| top_moversC | Biggest price movers on Polymarket |
| list_eventsC | List Polymarket events with child markets |
| market_narrativesB | Cluster Polymarket events by theme/narrative |
| detect_volume_spikesC | Detect Polymarket markets with unusual 24h volume |
| find_arbitrageB | Find arbitrage opportunities where Yes+No != 100% |
| market_summaryA | Get a comprehensive summary of the Polymarket ecosystem right now |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: detection of volume spikes, arbitrage, specific market details, events listing, narrative clustering, ecosystem summary, keyword search, top markets by volume, and top movers. No two tools overlap in functionality, so an agent can easily distinguish them.
Seven out of nine tools follow a consistent verb_noun pattern (e.g., detect_volume_spikes, get_market, search_markets). Two tools, market_narratives and market_summary, use a noun_noun format, which is a minor deviation but still clear.
With 9 tools, the server provides a broad yet focused set of functionalities for analyzing Polymarket prediction markets. The count is well-scoped for a single-purpose server, neither too few nor too many.
The tools cover key analytical tasks for Polymarket: searching, listing, summarizing, detecting anomalies, and identifying opportunities. For a read-only analysis server, the surface is complete; adding betting or account tools would shift scope.