Skip to main content
Glama

Find matched markets

find_matches
Read-onlyIdempotent

List prediction markets that are the same bet on Kalshi and another venue, earliest event day first, with both venues' live prices and the best trade between them. Filter with q (words in the title, such as nba or btc), series, category, and a date range. total says how many there are; while has_more is true, call again with offset=next_offset. An empty answer has a hint saying why.

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": "find_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords that must all appear in the market title, e.g. nba, bitcoin, fed. A coin's name (bitcoin, ethereum, solana, ripple) finds every market on that coin.
toNoLast event day, YYYY-MM-DD.
fromNoFirst event day, YYYY-MM-DD. Without it, events that ended over 12 hours ago are left out.
limitNoHow many to return. Start small (10 to 25): each match is a long object.
venueNoThe venue matched with Kalshi. Polymarket US when left out.
offsetNoHow many to skip: send next_offset from the last answer.
seriesNoKalshi series, comma-separated, e.g. KXBTC15M for 15-minute Bitcoin windows.
categoryNoOne category, e.g. sports, crypto, politics, economics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Words that must all appear in the market title, e.g. nba, btc, fed. Crypto markets use the ticker: btc, eth, sol, xrp."New value: +"Words that must all appear in the market title, e.g. nba, bitcoin, fed. A coin's name (bitcoin, ethereum, solana, ripple) finds every market on that coin."
  2. Changed1 schema field changed
    • changedInput schema / properties / from / description
      Previous value: -"First event day, YYYY-MM-DD."New value: +"First event day, YYYY-MM-DD. Without it, events that ended over 12 hours ago are left out."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so safety is covered. Beyond that, the description discloses ordering (earliest event day first), the pagination contract (total, has_more, next_offset), and that empty results include a reason hint — behavioral context not derivable from the annotations. It omits anything about rate limits or latency.

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?

Four sentences, front-loaded with the resource and sort order, then filtering, then pagination, then the empty-result case. Every sentence carries operational value with no filler. The prose is dense and slightly compressed (e.g., 'total says how many there are'), but nothing is wasted.

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?

With eight optional parameters and no output schema, the description does needed work by sketching the response shape (matched prices, best trade, total, has_more, next_offset, hint). The main remaining gap is that it never mentions the venue parameter or its default, leaving that entirely to the schema. Overall it is sufficient for an agent to call the tool correctly.

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 explains q, from, to, limit, offset, venue, series, and category, including defaults like venue falling back to Polymarket US. The description restates the filter set and the offset=next_offset loop but adds no format or semantics beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 opens with a precise verb and resource: 'List prediction markets that are the same bet on Kalshi and another venue,' plus what each entry carries (both venues' live prices and the best trade between them). That is far more specific than the title 'Find matched markets.' It never explicitly contrasts itself with the siblings check_profit or lookup_match, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives concrete operational guidance: filter with q, series, category, and a date range; watch total; and loop with offset=next_offset while has_more is true. It also notes that an empty answer carries a hint explaining why. It offers no explicit when-not-to-use conditions or named alternatives for the case where the agent should use lookup_match instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources