Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

polymarket_search

Search Polymarket events by query, then filter by open, closed, or all and sort by relevance, volume, liquidity, or end date to find matching prediction markets.

Instructions

Search Polymarket events. Searches Polymarket and returns event results. The status enum accepts open, closed, and all; the sort enum accepts relevance, volume24hr, volume, liquidity, and endDate.

Input Schema

Name	Required	Description
`q`	Yes	Search query
`sort`	No	Search sort
`limit`	No	Maximum events, defaults to 10 and supports up to 50
`status`	No	Event status filter
`ascending`	No	Sort ascending when true
`include_tags`	No	Include matching tags
`include_profiles`	No	Include matching profiles

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.17.5Sep 26, 2026

addedInput schema / properties / sort / enum

Added value: +[
+  "relevance",
+  "volume24hr",
+  "volume",
+  "liquidity",
+  "endDate"
+]

addedInput schema / properties / status / enum

Added value: +[
+  "open",
+  "closed",
+  "all"
+]

Addedv1.1.0Jun 12, 2026

TDQS

C2.8/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 behavioral burden, yet it discloses nothing beyond restating enum members already in the schema. No mention of pagination, default result behavior, freshness, or authentication needs for a 7-parameter search endpoint.

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 the second sentence ('Searches Polymarket and returns event results') is pure restatement, and the enum listings duplicate schema content. Two of three sentences do not earn their place.

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

Completeness2/5

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

For a 7-parameter search tool with no output schema and no annotations, the description is far too thin: it omits default limit behavior, how sort/ascending interact, and what an event result contains. The agent must fall back entirely on 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?

Schema description coverage is 100%, so the schema already documents every parameter including the enums. The description merely echoes the status and sort enum values, adding no syntax, ordering, or semantic detail beyond what the schema provides; baseline 3 applies.

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+resource ('Search Polymarket events') and repeats it as 'searches Polymarket and returns event results.' Clear on what it does, but gives no differentiation from the many sibling polymarket tools (e.g. polymarket_events, polymarket_event_detail, polymarket_predictions), so an agent can't tell when this search is preferred over them.

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 exclusions, and no routing to alternatives such as polymarket_events or polymarket_event_detail. Usage is only implied by the word 'Search,' leaving the agent to guess at scope versus the sibling list tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

polymarket_search

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools