mcp-server-polymarket

Overview Schema Source Related Servers Discussions Admin

Get an event

get_event

Read-onlyIdempotent

Retrieves a Polymarket event by ID or slug, returning its markets sorted by trading volume plus full description and tags.

Instructions

One event with its markets (most traded first), full description and tags. Give event_id or slug.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_event"
  }
}

Input Schema

Name	Required	Description
`slug`	No	URL slug, from polymarket.com/event/<slug>.
`event_id`	No	Numeric event id.
`max_markets`	No	Markets to include per event.
`include_counts`	No	Also fetch the comment and tweet counts.

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	No
`slug`	No
`tags`	No
`title`	No
`status`	No
`volume`	No
`markets`	No
`end_date`	No
`neg_risk`	No
`liquidity`	No
`start_date`	No
`volume_24h`	No
`description`	No
`series_slug`	No
`tweet_count`	No
`comment_count`	No
`markets_total`	No
`open_interest`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavioral detail beyond that, namely that markets come back sorted most-traded first and that the full description and tags are included, but it stays silent on what happens if both identifiers are given or neither is, and on truncation past max_markets.

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?

Two short sentences, front-loaded with what is returned before the invocation hint. No filler, no restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the annotations carry the safety profile, so the description does not need to explain return values. It covers the essentials for a single-entity read; the only nontrivial gap is that no identifier being supplied is not addressed, leaving the caller to discover the error mode at runtime.

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

Parameters4/5

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

Schema coverage is 100%, which sets a baseline of 3, but the description adds meaning the schema obscures: both slug and event_id are optional with null defaults in the schema, and the text clarifies that one of them must actually be supplied. It says nothing extra about max_markets or include_counts, but those are already well documented in the schema.

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 concrete verb and resource ('One event with its markets') plus the payload contents ('full description and tags'), which lets an agent separate it from the sibling get_market. It never names a sibling explicitly, so it stops short of a 5.

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?

'Give event_id or slug' implies the lookup pattern, so the agent knows how to invoke it, but there is no explicit when-to-use versus alternatives such as get_market or get_series, and no statement of what to do when no identifier is supplied.

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

Deploy Server