Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_events_similar

Find similar Polymarket prediction events by event ID, slug, or title. Returns normalized related events from public data to help discover comparable markets.

Instructions

Find similar Polymarket events. Returns normalized similar events from Polymarket's credential-free public Gamma events/similar JSON.

Input Schema

TableJSON 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.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose useful traits: the endpoint is 'credential-free' and 'public,' and results are 'normalized.' However, it doesn't mention read-only status, rate limits, or what 'similar' is based on, leaving some behavioral uncertainty.

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 concise sentences with the core action front-loaded and the source/credential detail in the second sentence. Every word earns its place; no fluff or repetition.

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?

With no output schema and no annotations, the description should explain what 'similar' means and which of the 7 optional parameters are required for a meaningful call, but it doesn't. It only states that normalized events are returned, leaving the agent to guess at minimal input requirements.

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 coverage is 100%, so the baseline is 3, and the description adds no parameter-level detail beyond the schema. The schema documents all 7 parameters, though the description doesn't clarify which combination is needed to perform a similarity lookup.

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 opens with a specific verb and resource ('Find similar Polymarket events') and adds the exact source endpoint ('Gamma events/similar JSON'), which distinguishes it from sibling tools like polymarket_events and polymarket_search. The term 'similar' makes the tool's unique role immediately clear.

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 phrase 'Find similar Polymarket events' implies the intended use case – finding related events – but the description provides no explicit guidance on when to prefer this over siblings, nor any exclusions or prerequisites. An agent must infer usage context from the 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