Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_activity_trades

List public Polymarket activity trades with filters for market, event, taker-only, and minimum cash amount to support trading activity analysis.

Instructions

List Polymarket activity trades. Returns public trade rows used by Polymarket's /activity page. The taker_only enum accepts true and false; the filter_type enum accepts CASH; the filter_amount enum accepts 1, 5, 10, 100, 1000, 10000, and 100000.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum trades, defaults to 50 and supports up to 100
marketNoOptional market condition id
offsetNoResult offset, defaults to 0 and supports up to 10000
event_idNoOptional Polymarket event id
taker_onlyNoTaker-only filter
filter_typeNoActivity amount filter type
filter_amountNoMinimum filtered amount

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / filter_amount / enum
      Added value: +[
+  "1",
+  "5",
+  "10",
+  "100",
+  "1000",
+  "10000",
+  "100000"
+]
    • addedInput schema / properties / filter_type / enum
      Added value: +[
+  "CASH"
+]
    • addedInput schema / properties / taker_only / enum
      Added value: +[
+  "true",
+  "false"
+]
  2. Addedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that results are public trade rows from the /activity page, which signals a read-only public endpoint, but it omits pagination behavior, ordering, rate limits, and auth requirements.

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?

The description is front-loaded and concise, but the third sentence enumerates enum values already present in the schema, which is redundant and does not earn its place.

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?

The tool has seven optional parameters, no output schema, and no annotations. The schema covers parameter semantics, but the description does not sufficiently explain return shape, pagination, or behavioral constraints for an agent to fully understand the endpoint.

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 only repeats enum values already defined in the schema and adds no extra meaning for market, event_id, limit, or offset.

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 activity trades, and clarifies these are public trade rows used by Polymarket's /activity page. It clearly identifies the tool's purpose, though it does not explicitly differentiate from sibling Polymarket 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 the tool is for public activity trades, but it gives no explicit when-to-use guidance, exclusions, or alternatives to sibling tools such as polymarket_markets or polymarket_event_detail.

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