Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

list_events

Retrieve Polymarket events with optional tag filters, pagination, sorting, and closed-event inclusion so you can locate and browse relevant prediction markets.

Instructions

List Polymarket events with optional filtering by tags, pagination, and sorting

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (max 100)
orderNoField to order by
closedNoInclude closed events
offsetNoPagination offset
tag_idNoFilter by tag ID
ascendingNoSort in ascending order
related_tagsNoInclude related tags
exclude_tag_idNoExclude specific tag IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it. It does not say whether closed events are excluded by default (the `closed` parameter's own text is ambiguous about the default), what the default page size is, whether authentication or rate limits apply, or what the response shape looks like.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity is partly the source of the coverage gaps rather than a virtue in itself.

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

Completeness2/5

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

For an eight-parameter listing tool with no annotations and no output schema, one sentence is thin: defaults for `limit`, `closed`, and `ascending`, plus result ordering and pagination behavior, are all left unresolved. An agent could call it, but would be guessing at several defaults that materially change 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?

Schema description coverage is 100%, so every one of the eight parameters already has documentation and the baseline is 3. The description groups the parameters into tags/pagination/sorting but adds no semantics beyond that grouping — no default values, no note on whether `closed` defaults true or false, no guidance on `related_tags` interaction with `tag_id`.

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 states a specific verb and resource ("List Polymarket events") and names the three axes of control (tags, pagination, sorting), so the agent knows this is a collection-listing endpoint rather than a lookup. It does not explicitly distinguish itself from siblings like get_event_by_slug or list_markets, but the verb/resource pairing is unambiguous enough to route correctly.

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?

There is no when-to-use guidance: nothing says when to prefer this over get_event_by_slug, list_markets, or search_polymarket, and no exclusions or prerequisites are given. The clause "with optional filtering by tags, pagination, and sorting" merely restates the input schema rather than advising how or when to apply those options.

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