Skip to main content
Glama

Search Polymarket prediction markets and their odds

prediction_polymarket
Read-only

Active Polymarket prediction markets matching search words, or one market by slug: the question, each outcome with its price as an implied probability, volume, liquidity, end date and link. Closed markets are left out. Source: Polymarket Gamma API. Information only, not financial advice. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch words, e.g. bitcoin
slugNoOr one market's slug
limitNo1 to 20 (default 5)

Output Schema

NameRequiredDescriptionDefault
queryNo
sourceNo
marketsNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond readOnlyHint and openWorldHint, the description discloses important behavior: only active markets are returned, closed markets are omitted, the data source is Polymarket Gamma API, and pricing is $0.002 per successful call via x402 with failed calls not charged. This is substantial operational context an agent needs before invoking a paid tool.

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 description is front-loaded with the core purpose and then adds filtering, source, disclaimer, and pricing details. It is dense but mostly earns its space; the legal disclaimer is less relevant to tool selection and invocation.

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?

Given the annotations, full schema coverage, and an existing output schema, the description supplies the remaining critical context: active-only filtering, source, pricing, and payment mechanics. Nothing essential for correct invocation appears to be 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 description coverage is 100%, so q, slug, and limit are already documented in the input schema. The description reinforces the q-versus-slug modes but adds little semantic detail beyond what the schema provides, making the baseline score appropriate.

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 states a specific resource and operation: active Polymarket prediction markets matching search words, or one market by slug, with odds and metadata. It is clear what the tool does, but it does not explicitly distinguish itself from similarly named sibling tools such as markets or pm_search.

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 description indicates two modes: search by words or retrieve one market by slug, and notes that closed markets are excluded. However, it gives no explicit when-to-use guidance versus alternatives and does not clarify behavior if both q and slug are supplied.

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