Skip to main content
Glama

Fetches recently resolved prediction markets

pm_resolved
Read-only

Fetches recently resolved prediction markets from Polymarket and Manifold over the last N days (max 30). Includes question, winning outcome, final prices/probabilities, resolution timestamp, and resolution source. Optional keyword filter. Information only, not financial advice. Related tools on this server, for a different need: pm_search when you need to search open prediction markets on Polymarket and Manifold; pm_activity when you need to fetch recent trading and on-chain lifecycle activity. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "days": "<days>"
    },
    "name": "pm_resolved"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional keyword filter
daysYesLookback window in days (1 to 30)
limitNoMaximum resolved markets to return (max 50)

Output Schema

NameRequiredDescriptionDefault
daysNo
countNo
sourceNo
checkedAtNo
disclaimerNo
venuesCheckedNo
resolvedMarketsNo
venuesUnavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses cost ($0.003 per successful call), the payment rail (x402/USDC on Base, Solana, and others), and that failed calls are not charged — behavior no annotation conveys. It also states the hard 30-day lookback bound, which materially shapes how the tool can be called.

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?

The core scope, returned fields, and sibling routing are front-loaded and each sentence carries information. It is slightly padded by the enumerated payment networks and the trailing pricing detail, which could be trimmed without loss.

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

Completeness5/5

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

With annotations covering safety, an output schema covering return values, and full schema coverage on the three parameters, the description's remaining burden is scope and alternatives — both handled explicitly. An agent has everything needed to decide and call correctly.

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 coverage is 100%, so all three parameters are already documented in the input schema, and the description largely restates what is there ('optional keyword filter', 'last N days (max 30)'). It adds no new detail on the limit parameter or filter matching semantics, so the baseline 3 applies.

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

Purpose5/5

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

The description opens with a specific verb and resource, 'Fetches recently resolved prediction markets from Polymarket and Manifold over the last N days (max 30)', and enumerates the returned fields (question, winning outcome, final prices, resolution timestamp, source). It also names the sibling tools that serve different needs, so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

It explicitly routes the agent: use pm_search for open markets and pm_activity for trading/on-chain lifecycle activity, leaving this tool for settled markets. The scoping constraint (resolved, max 30 days) and the 'information only' disclaimer are stated up front, so nothing key is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources