Skip to main content
Glama
jiroamato

Polymarket MCP Server

by jiroamato
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_active_markets

Read-only

Browse active prediction markets sorted by volume, liquidity, or expiration. Filter by category and minimum volume to find trending or expiring events.

Instructions

Browse active (open, unresolved) events sorted by a field.

Use this for discovery when the user asks "what's hot / most liquid / expiring soon" without naming a topic. For keyword search, use search_markets.

  • limit: Events to return (default 10, max ~100).

  • offset: Pagination offset (default 0). Page by incrementing offset by limit.

  • order: Sort field. Supported values:

    • "volume" — cumulative USD traded (default; "biggest overall")

    • "liquidity" — USD in the order book now ("where you can trade")

    • "end_date" — resolution deadline ("expiring soonest")

    • "start_date" — listing date

    • "competitive" — closest to 50/50 ("most contested"; best-effort semantics)

  • ascending: False (default) returns largest/latest first.

  • tag_slug: Category filter. Known slugs include "politics", "crypto", "sports", "elections", "geopolitics". Omit for all categories.

  • volume_min: Minimum cumulative USD volume. Useful to exclude long-tail markets with near-zero activity.

Returns a list of event dicts with nested markets. Each event has id, end_date, volume, volume_24hr, liquidity, and markets[]. Each nested market has id, outcomes, outcome_prices, best_bid, best_ask, last_trade_price.

Does NOT include event-level active / closed / category, or market-level closed / liquidity / one_day_price_change. Call get_market for those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
orderNovolume
offsetNo
tag_slugNo
ascendingNo
volume_minNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A5/5.0
Behavior5/5

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

Beyond readOnlyHint annotation, the description details return format (event dicts with nested markets), lists included and excluded fields, and clarifies no mutation occurs.

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?

Well-structured with clear sections, bullet points, and minimal redundancy. Every sentence adds value; it's appropriately detailed without being verbose.

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?

Given 6 parameters and output schema existence, the description provides complete context: input usage, return structure, and explicit list of excluded fields. No gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema coverage, description fully explains each of 6 parameters: limit/max, offset pagination, supported order values with definitions, ascending behavior, tag_slug examples, and volume_min usage.

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?

The description clearly states the tool browses active (open, unresolved) events sorted by field, distinguishes from search_markets for keyword search, and lists supported sort orders and their meanings.

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

Usage Guidelines5/5

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

Explicitly states when to use for discovery queries like 'what's hot' without a topic, and directs to search_markets for keyword search. Also explains pagination and ordering semantics.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jiroamato/polymarket_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server