Get Polymarket event
polymarket_event_getFetches a Polymarket event by ID or slug, returning all its markets, current prices, and resolution rules so you can inspect or compare prediction-market outcomes.
Instructions
Get a Polymarket event with all its markets, prices and resolution rules. Requires eventIdOrSlug.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"eventIdOrSlug": "<eventIdOrSlug>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "polymarket_event_get"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Translate titles and market questions into this language. Descriptions stay in English. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| include | No | Extras to add, comma separated: `insights` (the written market context) and `annotations` (dated explanations of price moves). Each is one extra lookup and can be absent, in which case it is null. | |
| llm_model | Yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess. | |
| eventIdOrSlug | Yes | Required. Event id (digits) or slug, as in polymarket.com/event/{slug}. | |
| conversation_id | No | Echo the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it. |