mcp-server-polymarket

Overview Schema Source Related Servers Discussions Admin

Get a series

get_series

Read-onlyIdempotent

Fetches a Polymarket series by slug or ID, returning recent events and recurrence frequency; supports summary-only output.

Instructions

One series with its most recent events and how often it recurs.

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

Input Schema

Name	Required	Description
`slug`	No
`series_id`	No	Numeric series id.
`max_events`	No	Recent events to include.
`summary_only`	No	Only id, title and event dates, without events.

Output Schema

Name	Required	Description	Default
`id`	Yes
`slug`	No
`title`	No
`events`	No
`status`	No
`volume`	No
`liquidity`	No
`recurrence`	No
`volume_24h`	No
`description`	No
`event_dates`	No
`series_type`	No
`events_total`	No
`comment_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

C2.5/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds only a hint of return content (recent events, recurrence), which duplicates the output schema and says nothing about pagination, missing identifiers, or lookup failure behavior.

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?

One short sentence with no filler, but it is under-specified rather than efficient; the reader still has to open the schema to learn how to address a series.

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?

With four optional parameters and no required fields, the critical fact an agent needs is that it must pass slug or series_id, which the description never states. An output schema exists, so return values need not be explained, but identifier requirements are a real gap.

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 75%, so the schema largely documents max_events and summary_only itself. The description's 'most recent events' loosely maps to max_events but adds no default, cap, or interplay details, and is silent on slug vs series_id selection.

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

Purpose3/5

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

The sentence identifies the resource ('One series') and what comes back (recent events plus recurrence cadence), but it is a noun phrase with no verb and never contrasts with the sibling list_series. An agent can guess this is the singular fetch, but the description does not state it explicitly.

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, no mention of list_series as the plural alternative, and no note that the caller must supply an identifier. Usage must be inferred entirely from the name and schema.

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

Deploy Server