Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_events_similar

Find Polymarket events similar to a given event by id, title, or slug. Filter results by closed status and set a limit to compare related markets.

Instructions

Find similar Polymarket events. Finds Polymarket events similar to a given one. Supply at least one of id, event_title, event_slug, market_title or market_slug; limit defaults to 10 (max 50) and closed (true or false) filters by closed state. Each event has its title, dates, volume, liquidity, tags and nested markets.

Input Schema

NameRequiredDescriptionDefault
idNoPolymarket event id
limitNoMaximum events, defaults to 10 and supports up to 50
closedNoClosed filter
event_slugNoEvent slug
event_titleNoEvent title
market_slugNoMarket slug
market_titleNoMarket title

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / closed / enum
      Added value: +[
+  "true",
+  "false"
+]
  2. Addedv1.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses returned fields (title, dates, volume, liquidity, tags, nested markets) and the max limit, but does not describe similarity logic, error behavior, auth needs, or pagination.

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 compact and front-loads the core purpose, then moves into invocation details and return contents. The first two sentences are slightly redundant, but the overall structure is efficient.

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?

For a seven-parameter tool with no annotations and no output schema, the description supplies the key missing context: identifier requirements, limit bounds, closed filtering, and the shape of returned events. Minor gaps remain around similarity behavior and failure modes, but the essential guidance is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents each parameter. The description adds an important constraint not expressed in the schema: at least one of id, event_title, event_slug, market_title, or market_slug must be supplied.

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 gives a specific verb and resource: it finds Polymarket events similar to a given event. The phrase "similar to a given one" distinguishes it from sibling tools that list events or return a single 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 Guidelines3/5

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

It states the core invocation requirement: supply at least one identifier, and documents limit and closed filtering. However, it does not explicitly say when to use this tool versus alternatives such as polymarket_events or polymarket_search.

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