Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_rewards_markets

Fetch Polymarket rewards markets by date, category, and sort order to compare earnings, spreads, sizes, and daily rates.

Instructions

List Polymarket rewards markets. Returns 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
qNoOptional market question search text
dateNoReward program date in YYYY-MM-DD format; defaults to today in UTC
limitNoMaximum rows, defaults to 100 and supports up to 100
cursorNoOptional rewards cursor from a prior response; defaults to MA==
order_byNoRewards market sort
positionNoSort direction
tag_slugNoRewards category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / order_by / enum
      Added value: +[
+  "market",
+  "earnings",
+  "max_spread",
+  "min_size",
+  "rate_per_day",
+  "price",
+  "earning_percentage",
+  "spread"
+]
    • addedInput schema / properties / position / enum
      Added value: +[
+  "asc",
+  "desc"
+]
    • addedInput schema / properties / tag_slug / enum
      Added value: +[
+  "all",
+  "politics",
+  "sports",
+  "crypto",
+  "pop-culture",
+  "middle-east",
+  "business",
+  "science"
+]
  2. Addedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It notes the rows are 'public' (helpful), but says nothing about rate limits, pagination continuation semantics beyond the schema's cursor, result ordering defaults, or what the response looks like for a read tool with a cursor.

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?

Purpose is front-loaded in the first sentence, but roughly two-thirds of the text is spent re-listing enum values that already exist verbatim in the schema. That is padding that crowds out more useful content rather than genuinely concise phrasing.

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 7-param, zero-annotation, no-output-schema list tool, the description establishes purpose and enumerates filter options but omits pagination behavior, default sort, and safety/mutation expectations. Adequate but leaves gaps an agent would want filled.

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 the baseline is 3. The description merely restates the three enum value sets already fully enumerated in the schema, adding no syntax, defaulting, or interaction semantics (e.g., how order_by and position combine) beyond what structured fields provide.

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 rewards markets') and clarifies the data is the public rewards-market rows behind the /rewards page. It does not differentiate itself from siblings like polymarket_rewards_market (singular), polymarket_markets, or polymarket_market_tags, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no named alternatives. The singular sibling polymarket_rewards_market is the obvious confusion point and is never addressed, leaving the agent with no routing information.

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