Skip to main content
Glama

Search open prediction markets on Polymarket and Manifold

pm_search
Read-only

Searches open prediction markets on Polymarket (real money, USDC) and Manifold (play money) by keywords, with optional closing-date window and minimum volume. Each row: venue, question, outcomes with prices (implied probability), volume with its unit (USD or mana), liquidity, close time and link. Results alternate between venues; up to 50 rows. Information only, not financial advice. Usually answers in a few seconds, up to 15 s on slower calls; allow a 30 s timeout. Related tools on this server, for a different need: pm_resolved when you need to fetch recently resolved prediction markets; pm_wallet when you need open positions of a Polymarket wallet: market, outcome. 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": {
      "q": "<q>"
    },
    "name": "pm_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch words, e.g. fed, election, bitcoin
limitNoMarkets to return, 1 to 50, default 20
venueNoall (default), polymarket or manifold
minVolumeNoMinimum volume in the venue's own unit (USD on Polymarket, mana on Manifold)
closeAfterNoOnly markets closing on or after this date, YYYY-MM-DD
closeBeforeNoOnly markets closing on or before this date, YYYY-MM-DD

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
sourceNo
marketsNo
checkedAtNo
disclaimerNo
venuesCheckedNo
venuesUnavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / count
      Added value: +{}
    • removedOutput schema / properties / total
      Removed value: -{}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds far more — cross-venue result interleaving, a 50-row cap, expected latency (seconds, up to 15 s) with a 30 s timeout recommendation, and a pay-per-call model at $0.003 charged only on success via x402. These are operational facts an agent cannot get from the annotations.

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?

Front-loaded with purpose, then return-row contents, then limits, then cost/latency, then sibling routing — a sensible ordering with no filler sentences. It is dense and slightly list-like, and the "not financial advice" clause and the verbose payment breakdown could be tightened without losing meaning.

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?

For a read-only, open-world search with an output schema and six documented params, the definition covers what an agent still needs: row composition, result ordering across venues, row cap, latency/timeout, and pricing. Nothing required to invoke it correctly is missing.

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 every parameter is already documented, including the venue-specific volume unit and the date formats. The description only echoes the closing-date window and minimum volume at a high level and adds no syntax, defaults, or interaction rules beyond the schema, 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?

Opens with a specific verb and resource — "Searches open prediction markets" — and names both venues (Polymarket with USDC, Manifold with play money) plus the supported filters. It also implicitly distinguishes itself from pm_resolved by scoping to *open* markets, so an agent can tell it apart from its nearest sibling.

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?

The description explicitly routes the agent to alternatives with their triggering conditions: pm_resolved "when you need to fetch recently resolved prediction markets" and pm_wallet "when you need open positions of a Polymarket wallet." That is a concrete when-to-use-this-instead statement rather than vague context.

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