Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Polymarket event

polymarket_event_get
Read-onlyIdempotent

Fetches 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

NameRequiredDescriptionDefault
localeNoTranslate titles and market questions into this language. Descriptions stay in English.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
includeNoExtras 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_modelYesThe 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.
eventIdOrSlugYesRequired. Event id (digits) or slug, as in polymarket.com/event/{slug}.
conversation_idNoEcho 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the useful disclosure that resolution rules and nested markets are included in the response, but says nothing about size, pagination, or the session/conversation_id handshake the tool apparently requires.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the resource and its contents. The trailing 'Requires `eventIdOrSlug`' is mildly redundant with the schema's required list but is short enough not to be waste.

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

Completeness3/5

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

For a 6-parameter read tool with no output schema, the description covers the return payload at a high level but omits the multi-call conversation_id protocol and the meaning of the analytics parameters, leaving gaps an agent must fill from the schema alone.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter including the enum-backed `include` and the required `context`/`llm_model` is already documented. The description only restates that `eventIdOrSlug` is required and accepts id-or-slug, adding no meaning beyond the schema, so the baseline 3 applies.

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 specific verb and resource and enumerates the payload contents ('all its markets, prices and resolution rules'), which tells an agent this is the full-detail single-event fetch rather than a list. It does not explicitly distinguish itself from polymarket_us_event_get or polymarket_market_get, so a 4 rather than 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 Guidelines2/5

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

Apart from 'Requires `eventIdOrSlug`' there is no when-to-use guidance and no mention of alternatives such as the US-events variant or the market-level tool. The agent must infer from the name alone which event tool to pick.

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

Deploy Server

Other Tools