Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_predictions

List Polymarket prediction events with filters for status, tag, recurrence, and sorting by volume, liquidity, ending soon, or newest; supports cursor pagination and up to 100 results.

Instructions

List Polymarket predictions. Returns event rows for the Polymarket /predictions page. 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

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

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It states the return shape ('event rows') but says nothing about pagination/cursor behavior, authentication, rate limits, or how the enums interact (e.g., does status='all' ignore recurrence). Enum restatements duplicate the schema rather than adding behavioral context.

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

Conciseness3/5

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

Front-loaded and readable, but the second and third sentences mostly re-enumerate enum values already present in the schema, which is low-value text. It is not bloated enough to be harmful, but it is not lean either.

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?

For a 6-param list tool with no output schema but full schema coverage, the description covers the return type and filter enums. It omits pagination semantics and sibling routing, which are the meaningful gaps given how many polymarket tools exist.

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% and three parameters carry enums already enumerated in the schema, so the description adds little beyond it. The re-listing of status/sort/recurrence values is redundant with structured data; baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('List Polymarket predictions') and anchors it to a concrete source ('the Polymarket /predictions page'), so the agent knows exactly what is returned. It does not, however, distinguish this from the many polymarket siblings such as polymarket_events, polymarket_markets, or polymarket_homepage_feed.

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 reference to returning 'event rows for the Polymarket /predictions page' implies a browse/homepage-style use case, but there is no explicit when-to-use, when-not-to-use, or named alternative among the dozens of polymarket_* siblings. Usage must be inferred.

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