mcp-server-polymarket

Overview Schema Source Related Servers Discussions Admin

List series

list_series

Read-onlyIdempotent

List recurring Polymarket event series, such as sports seasons or daily crypto markets, with filters for status, category, and recurrence plus cursor-based pagination.

Instructions

A series is a recurring set of events, such as an NFL season or daily crypto markets.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Rows per page.
`cursor`	No	next_cursor from the previous page. Empty starts at the top.
`status`	No		open
`category`	No	Category label, e.g. Sports.
`recurrence`	No	e.g. daily, weekly.

Output Schema

Name	Required	Description	Default
`note`	No
`count`	No
`items`	No
`has_more`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

C2.1/5.0

Behavior2/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context such as the default status of 'open', how pagination works, or what the results represent beyond the generic series concept.

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

Conciseness3/5

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

The single sentence is concise and contains no filler, but it is not front-loaded with the tool's action or purpose. It spends its only line defining a term rather than telling an agent what the tool does.

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 a list tool with five optional filters, pagination, and an output schema, the description omits essential context such as the default status filter and how category/recurrence narrow results. It is not complete enough to help an agent invoke the tool confidently beyond the schema and annotations.

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 80%, so the input schema already documents limit, cursor, category, and recurrence. The description contributes no additional parameter meaning beyond the schema's own definitions, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description defines what a series is ('a recurring set of events') but never states that this tool lists or returns series. The action is only implied by the tool name, and there is no explicit differentiation from the sibling get_series.

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

Usage Guidelines1/5

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

The definition gives no guidance on when to use list_series versus get_series or any other sibling. It does not explain how the status, category, or recurrence filters should be used to narrow results.

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

Deploy Server