Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_markets

Retrieve normalized Polymarket market data with filters for limit, sort order, closed status, and offset. Returns clean JSON rows for analysis.

Instructions

List Polymarket markets. Returns normalized market rows from Polymarket's credential-free public Gamma markets JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum markets, defaults to 25 and supports up to 100
orderNoSort field
closedNoClosed filter
offsetNoResult offset, defaults to 0 and supports up to 10000
ascendingNoSort ascending when true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / closed / enum
      Added value: +[
+  "true",
+  "false"
+]
    • addedInput schema / properties / order / enum
      Added value: +[
+  "volume24hr",
+  "volume",
+  "liquidity",
+  "endDate",
+  "updatedAt",
+  "createdAt",
+  "id",
+  "slug",
+  "title",
+  "question",
+  "label"
+]
  2. Addedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It adds that the output is 'normalized market rows' and is 'credential-free public', which gives some behavioral insight. It does not disclose pagination, rate limits, or what normalization entails, but it is adequate for a read-only listing tool.

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?

A single, well-structured sentence that front-loads the core action and source. No wasted words; it is concise and immediately informative.

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

Completeness4/5

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

Given no output schema, the description indicates the return type ('normalized market rows'), and the schema covers all parameters. The tool's simplicity means this is largely complete, though it could mention default pagination limits or sorting, which are already in the 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?

All 5 parameters are fully documented in the schema (100% coverage), so the baseline is 3. The description adds no additional parameter semantics beyond noting the source and normalization, which is sufficient.

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 identifies the tool as listing Polymarket markets, and distinguishes it from related market-specific tools by specifying it returns normalized market rows from Gamma JSON. The verb 'List' and resource are explicit.

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

Usage Guidelines4/5

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

The description provides useful context ('credential-free public') that signals no authentication is needed opportunistically. However, it does not explicitly mention when to prefer this over sibling tools like polymarket_events or polymarket_market_detail, nor does it state exclusions. The context is clear but lacks explicit routing guidance.

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