Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_markets

Query Polymarket prediction markets with sorting by volume or liquidity, pagination, and closed-status filtering to research prices, outcomes, and token data.

Instructions

List Polymarket markets. Lists Polymarket markets, up to limit rows (default 25, max 100), starting at offset (default 0, max 10000). Sort with order, such as volume24hr or liquidity, flip direction with ascending, and filter with closed. Each market has its question, slug, prices, volume, liquidity, token ids and outcomes.

Input 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

A3.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses pagination limits (default 25, max 100; offset max 10000), sorting options, filtering, and the fields returned for each market. It stops short of explicitly stating that the operation is read-only or describing auth/rate-limit behavior, but for a list endpoint the disclosed constraints and return shape are substantial.

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 and reasonably sized. The only waste is the initial sentence 'List Polymarket markets.' immediately followed by 'Lists Polymarket markets, ...' which repeats the same idea. Otherwise, each sentence carries useful information about pagination, sorting, filtering, and returned fields.

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?

With no output schema and no annotations, the description needs to supply enough context for correct invocation. It covers pagination, sorting, filtering, and the shape of returned market records, which is enough for a list tool. Minor gaps remain, such as the default closed-state behavior and whether pagination has a total count, but the description is largely complete.

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 schema already documents every parameter and its defaults. The description adds a couple of example order values ('volume24hr', 'liquidity') and reinforces pagination defaults, but adds little beyond the schema. Baseline 3 is appropriate 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?

The description states a specific verb and resource: 'List Polymarket markets.' This clearly distinguishes it from detail-oriented siblings like polymarket_market_detail or query-oriented tools like polymarket_search. However, it does not explicitly name or compare itself to any sibling, so the differentiation is implicit rather than explicit.

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 explains how to use pagination, sorting, and filtering, which implies the tool is for browsing markets. It does not state when to use this tool versus alternatives such as polymarket_search or polymarket_events, nor does it provide exclusions. Usage is therefore implied rather than guided.

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