Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Polymarket series

polymarket_series_get
Read-onlyIdempotent

Fetch a single Polymarket series by id or slug, optionally including its recent events and market numbers for context.

Instructions

Get one Polymarket series and, on request, its recent events. Requires idOrSlug.

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": {
      "idOrSlug": "<idOrSlug>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_series_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
idOrSlugYesRequired. Series id (digits) or slug.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
includeEventsNoAdd the series' most recent events with their markets' headline numbers (one more lookup). Default: false.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is fully covered. The description adds that events are fetched only 'on request', hinting at extra cost, but never states the payload shape, whether markets/volume fields come back, or what happens on an unknown id or slug.

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 zero filler. Brevity is the right call given the schema documents every parameter, though it borders on under-specified for a tool with an optional expansion path.

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?

There is no output schema, so the description could say more about what a series object contains and what the includeEvents expansion returns. Against that, the tool is a simple read-only single-record fetch, and the schema's parameter descriptions (including conversation_id sequencing and analytics fields) cover the calling mechanics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and every parameter (idOrSlug, context, llm_model, includeEvents, conversation_id) carries its own detailed description, so the baseline is 3. The description's only parameter remark, that idOrSlug is required, is already in the schema, and it adds no syntax or formatting detail of its own.

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?

States a specific verb and resource (get one series) plus the optional inclusion of its recent events. Singular 'one series' implicitly contrasts with the sibling polymarket_series_list, but that sibling is never named.

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 word 'one' and the required idOrSlug imply this is a single-record lookup keyed by id or slug, which distinguishes it from a listing call. However, there is no explicit when-to-use or when-not guidance, and no named alternative (e.g. polymarket_event_get for drilling into an event) is mentioned.

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

Deploy Server

Other Tools