graph-polymarket-mcp

Overview Schema Source Related Servers Discussions Admin

get_polymarket_event

Retrieve a single Polymarket event and its associated markets by event ID or slug. Use to explore related prediction markets grouped under one topic.

Instructions

Get a single Polymarket event with all its associated markets. An event groups related prediction markets under one topic.

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": {
      "eventId": "<eventId>"
    },
    "name": "get_polymarket_event"
  }
}

Input Schema

Name	Required	Description	Default
`eventId`	Yes	Event ID or slug

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description fully carries the transparency burden. It discloses the core behavior (fetching a single event and all its markets) and explains the event's structure. While it doesn't mention edge cases or response details, it's sufficiently transparent for a simple read operation.

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?

The description is two short sentences with the key action front-loaded. Every word adds value, with no redundancy or filler. It achieves maximum clarity in minimal space.

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?

The description explains what an event is and that the tool returns all associated markets, which is sufficient for a single-parameter retrieval tool. It lacks an explicit return value list, but no output schema exists, so the description carries this responsibility adequately. Minor omission: doesn't mention that 'eventId' can be a slug, but that's in the schema.

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?

The input schema covers 100% of parameter semantics with a description for 'eventId' ('Event ID or slug'). The tool description adds no parameter-specific information, but the schema already provides the needed meaning, so the baseline score of 3 applies.

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 uses a specific verb ('Get') and resource ('Polymarket event') and clearly states it returns all associated markets. This distinguishes it from sibling tools like list_polymarket_events and search_polymarket_events, which operate at the collection level.

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

Usage Guidelines4/5

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

The description implies usage: call this when you have a specific event ID or slug and need all related markets. It clarifies the event concept, giving context for choosing this over list/search. However, it doesn't explicitly state when not to use it or name alternatives.

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