Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

polymarket_predictions

Fetch Polymarket predictions with status, sort, and recurrence filters. Returns normalized event rows from the /predictions page for competitive, volume, or newest markets.

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
cursorNoOptional keyset cursor from a prior predictions response
limitNoMaximum events, defaults to 20 and supports up to 100
recurrenceNoOptional recurrence filter
sortNoPrediction sort
statusNoPrediction status
tagNoOptional tag slug
Behavior3/5

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

No annotations provided, so the description carries full burden. It mentions credential-free access and lists enum values but does not disclose rate limits, mutation behavior, or pagination details beyond cursor/limit.

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?

Two concise sentences: first states purpose, second explains key parameters. Front-loaded with no extraneous information.

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 tool with 6 optional params and no output schema, the description covers purpose, data source, and enums, but omits description of return value structure (e.g., fields of normalized event rows). Could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds meaningful context by listing all enum values for status, sort, and recurrence, and clarifying cursor and limit behavior. This supplements the terse schema descriptions.

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 the tool lists Polymarket predictions, specifies the data source (Gamma events/keyset JSON for /predictions page), and distinguishes from siblings like polymarket_events or polymarket_markets by focusing on predictions.

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 does not explicitly guide when to use this tool versus alternatives. While the enum details help, there is no comparison with similar Polymarket tools or conditions for preferred use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server