polymarket-trader-mcp

markets.related

Find Polymarket markets related to a condition ID or keyword. Discover correlated markets to build diversified positions across related events.

Instructions

Find Polymarket markets related to a given condition_id or topic keyword. Useful for discovering correlated markets or building a diversified position across related events.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "markets.related"
  }
}

Input Schema

Name	Required	Description
`condition_id`	No	Find markets related to this market
`query`	No	Keyword to find related markets (e.g. 'bitcoin', 'trump')
`limit`	No	Maximum number of related markets to return

Schema Changelog

Changes observed during successful MCP inspections.

AddedApr 30, 2026

TDQS

A3.5/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 full burden. It fails to disclose behavioral traits like rate limits, authentication needs, or side effects. Only the purpose is stated, omitting any operational constraints or return structure.

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?

The description is two sentences long, front-loads the core purpose in the first sentence, and adds a use-case in the second. Every word is efficient with no 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?

Given no output schema and no annotations, the description is moderately complete: it explains inputs and purpose but lacks information about the output format or pagination. With three parameters and no required fields, it could hint at what the response looks like.

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%, with each parameter having a basic description. The tool description adds context about 'related' markets and use cases, but does not significantly enhance understanding beyond the schema since the schema already conveys parameter meanings clearly.

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 clearly states the verb 'Find' and the resource 'Polymarket markets', and distinguishes the tool by specifying the two modes of relating (by condition_id or topic keyword). It also notes utility in discovering correlated markets, differentiating it from sibling tools like markets.search or markets.featured.

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 use when wanting related markets ('useful for discovering correlated markets...') but does not explicitly state when not to use or compare to alternatives such as markets.search or markets.trending. The guidance is present but lacks exclusion criteria.

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