Skip to main content
Glama
Sign In
mcp-server-polymarket

mcp-server-polymarket

by tukorama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get resolution state

get_resolutions
Read-onlyIdempotent

Retrieve a prediction market's resolution status, including proposed price, disputes, final outcome, and expected settlement time by event, question, or condition IDs.

Instructions

Where each market is in resolution: proposed price, disputes, final outcome and the expected settlement time. Give exactly one of condition_ids, question_ids or event_id.

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

Input Schema

NameRequiredDescriptionDefault
event_idNo
question_idsNo
condition_idsNoUp to 20 condition ids.

Output Schema

NameRequiredDescriptionDefault
noteNo
countNo
itemsNo
has_moreNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description usefully signals what the payload concerns (proposed price through final settlement time), but says nothing about behavior when a market is unresolved, in dispute, or has no settlement estimate.

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

Conciseness5/5

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

Two sentences, both earning their place: the first front-loads the content contract, the second the input constraint. No filler or restatement of the title.

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?

With an output schema covering return values and annotations covering the safety profile, the description only needs to add the input contract and scope, which it largely does. The remaining gap is the lack of guidance on the three selectors' relative trade-offs and behavior for unresolved markets.

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

Parameters4/5

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

Schema coverage is low (33%) — only condition_ids carries a schema description — so the description must compensate, and it does by imposing a mutual-exclusivity rule ('exactly one of') that is absent from the schema, which allows all three to be null. It still omits that question_ids and event_id are unconstrained or single-valued.

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 names a specific resource (market resolution state) and enumerates the returned facets: proposed price, disputes, final outcome, expected settlement time. It is clearly distinct from settlement-agnostic siblings like get_market, though it frames the tool by output rather than by an explicit verb.

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?

The only guidance is the input constraint 'Give exactly one of condition_ids, question_ids or event_id.' There is no statement of when to reach for this tool versus get_market or get_event, nor any note on when resolution data is unavailable or premature.

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