Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

polymarket_rewards_markets

List rewards markets from Polymarket, filterable by date, tag, and sort criteria, returning normalized rows for reward program tracking.

Instructions

List Polymarket rewards markets. Returns normalized public rewards-market rows used by Polymarket's /rewards page. The order_by enum accepts market, earnings, max_spread, min_size, rate_per_day, price, earning_percentage, and spread; the position enum accepts asc and desc; the tag_slug enum accepts all, politics, sports, crypto, pop-culture, middle-east, business, and science.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoOptional rewards cursor from a prior response; defaults to MA==
dateNoReward program date in YYYY-MM-DD format; defaults to today in UTC
limitNoMaximum rows, defaults to 100 and supports up to 100
order_byNoRewards market sort
positionNoSort direction
qNoOptional market question search text
tag_slugNoRewards category
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions data source and normalization but fails to explain pagination semantics, data freshness, rate limits, or authorization needs. The cursor parameter hints at pagination, but the description does not elaborate.

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 main purpose and efficiently lists enum values. While it contains some redundancy (e.g., 'Rewards market sort' could be omitted), it remains clear and reasonably concise.

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?

Given no annotations and no output schema, the description adequately covers the tool's purpose and parameter values but lacks details on response structure, error handling, and pagination behavior. It meets the minimum for a moderately complex tool but is not fully comprehensive.

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 description coverage is 100%, setting a baseline of 3. The description adds value by explicitly listing the accepted values for order_by, position, and tag_slug enums, which goes beyond the schema's generic 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 starts with 'List Polymarket rewards markets,' providing a clear verb+resource combination. It further specifies that it returns 'normalized public rewards-market rows used by Polymarket's /rewards page,' distinguishing it from sibling tools like polymarket_rewards_market (singular) and other polymarket listing tools.

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 implies usage for listing rewards markets via the /rewards page but does not explicitly state when to use this tool over alternatives or provide exclusion criteria. No guidance on prerequisites or non-use cases is given.

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