Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_events

Retrieve normalized Polymarket prediction events from public Gamma data. Filter by closed status, sort by volume, liquidity, or date, and paginate results for market analysis.

Instructions

List Polymarket events. Returns normalized event rows from Polymarket's credential-free public Gamma events JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum events, 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

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral burden. It usefully discloses that the data source is credential-free and public, and that the output consists of normalized event rows, implying a read-only list operation. However, it does not explain pagination behavior, defaults, or what normalization entails relative to the raw API response.

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 short sentences with the core action front-loaded. The second sentence adds useful source and normalization context without redundancy.

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 list endpoint with no required parameters and a fully documented schema, the description is mostly adequate for making a basic call. However, with no output schema, 'normalized event rows' is vague about returned fields, and there is no guidance on how this tool relates to the many sibling Polymarket tools.

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 all five optional parameters with types, enums, and defaults. The description adds no parameter-level meaning beyond the schema, which is acceptable under the baseline.

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 uses a specific verb and resource ('List Polymarket events') and adds that it returns normalized event rows from the public Gamma events JSON. This distinguishes it from related market/token tools, though it does not explicitly name or contrast with sibling tools such as polymarket_markets or polymarket_event_detail.

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 guidance is provided on when to use this tool versus alternatives like polymarket_events_similar, polymarket_markets, or polymarket_event_detail. There are no exclusions, prerequisites, or selection criteria, so the agent must infer usage from the tool name alone.

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