graph-polymarket-mcp

Overview Schema Source Related Servers Discussions Admin

list_polymarket_events

Fetch Polymarket event groups, each bundling related yes/no markets. Filter by tag, activity, or sort by volume and liquidity.

Instructions

List Polymarket events (groups of related markets). Events bundle multiple Yes/No markets under one topic (e.g. 'US Presidential Election 2024' contains many candidate markets). Uses the Gamma API.

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": "list_polymarket_events"
  }
}

Input Schema

Name	Required	Description
`tag`	No	Filter by tag (e.g. 'politics', 'crypto', 'sports')
`limit`	No	Number of events (1-100)
`active`	No	Filter: only active events
`closed`	No	Filter: only closed events
`orderBy`	No	Sort field
`ascending`	No	Sort ascending

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 3, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions the data source ('Uses the Gamma API') but does not disclose read-only semantics, default filtering behavior (e.g., whether only active events are returned), pagination, or response format. The concept of events bundling markets is useful context but not a behavioral disclosure.

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?

The description is concise with three short sentences, front-loading the action. The final sentence 'Uses the Gamma API' adds little value for selection and invocation, slightly detracting from conciseness.

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?

While the purpose is clear and the schema is comprehensive, the description lacks information about the response format (no output schema), default behaviors, and alternatives to sibling tools. This leaves some gaps for an agent trying to correctly invoke and interpret results.

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 provides detailed descriptions for all 6 parameters including defaults, ranges, and enums (100% schema coverage). The tool description adds no additional parameter semantics beyond the schema, so the baseline score of 3 is appropriate.

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?

The description clearly states the tool's function with a specific verb ('List') and resource ('Polymarket events'), and clarifies that events are groups of related markets with a concrete example. However, it does not explicitly distinguish this from the sibling tool 'search_polymarket_events', so it lacks explicit sibling differentiation.

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?

The description implies the tool is used for listing all Polymarket events, but it provides no explicit guidance on when to use it versus searching/filtering via siblings like 'search_polymarket_events', and no exclusions are stated. Usage is only implied by the verb 'List'.

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