Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_predictions

Retrieve normalized Polymarket prediction events with filters for status, sort, recurrence, and pagination. Returns clean JSON for market analysis.

Instructions

List Polymarket predictions. Returns normalized event rows for the Polymarket /predictions page using credential-free Gamma events/keyset JSON. The status enum accepts active, resolved, and all; the sort enum accepts competitive, volume, volume_24hr, ending_soon, liquidity, newest, and closed_time; the recurrence enum accepts hourly, daily, weekly, monthly, and yearly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoOptional tag slug
sortNoPrediction sort
limitNoMaximum events, defaults to 20 and supports up to 100
cursorNoOptional keyset cursor from a prior predictions response
statusNoPrediction status
recurrenceNoOptional recurrence filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / recurrence / enum
      Added value: +[
+  "hourly",
+  "daily",
+  "weekly",
+  "monthly",
+  "yearly"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "competitive",
+  "volume",
+  "volume_24hr",
+  "ending_soon",
+  "liquidity",
+  "newest",
+  "closed_time"
+]
    • addedInput schema / properties / status / enum
      Added value: +[
+  "active",
+  "resolved",
+  "all"
+]
  2. Addedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It mentions 'credential-free' and the backend, but does not disclose read-only nature, pagination behavior, rate limits, or response structure. It adds some context but not comprehensive behavioral traits.

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?

The description is a single compact paragraph that front-loads the purpose and then lists the enums. Every sentence earns its place, no fluff. It is well-structured and easy to scan.

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

Completeness3/5

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

The description covers the core function and parameter enums, but with no output schema and no annotations, it lacks details on the return format (what fields are in 'normalized event rows'), pagination behavior (how cursor works), and potential errors. It is adequate but incomplete for a tool with 6 parameters and no output schema.

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 baseline is 3. The description repeats the enum values for status, sort, and recurrence but adds no new meaning beyond what the schema already provides. It does not explain the semantics of each sort option or when to use them.

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 clearly states it lists Polymarket predictions and returns normalized event rows for the /predictions page, using specific verb 'List' and resource. It distinguishes from other Polymarket tools by naming the exact page and backend (Gamma events/keyset). This is unambiguous.

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 gives no explicit guidance on when to use this tool versus other Polymarket tools like polymarket_events or polymarket_markets. It implies use for predictions but does not state exclusions or alternatives, which is a gap given the large sibling set.

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