Polymarket Gamma MCP Server
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 |
|---|---|
| get_trending_marketsA | Get trending/popular markets with highest volume and liquidity |
| get_sports_eventsC | Получить спортивные события с Polymarket (ПРАВИЛЬНЫЕ параметры) |
| get_markets_by_categoryA | Get markets filtered by category/tags (Politics, Sports, Crypto, etc.) |
| search_marketsA | Search markets by text query in question/description |
| get_market_detailsB | Get detailed information about a specific market by ID |
| get_eventsB | Get events with their associated markets |
| get_event_detailsA | Get detailed information about a specific event by ID |
| get_api_usageA | Get current API usage statistics and rate limits |
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 8 tools
Most tools are distinct: trending, category, search, details, events, event details, API usage. However, get_events and get_sports_events overlap somewhat, though the descriptions clarify sports is a subset. Search and category are clearly different. Overall, boundaries are mostly clear.
All tools follow the consistent pattern of 'get_' + noun, with clear nouns like 'trending_markets', 'market_details', 'events', etc. No mixed conventions or unexpected verbs.
8 tools are well-scoped for a read-only market data server. Each covers a distinct query type, and none feel redundant or excessive.
The surface covers market retrieval (trending, by category, search), market details, event listings and details, and API usage. Minor gaps like historical price data or market resolution info exist, but core read-only workflows are complete.