Skip to main content
Glama
predmarket-mcp

predmarket-mcp

compare_venues

Read-only

Search Kalshi and Polymarket for markets asking the same question, pair likely matches, and show the cross-venue price gap so you can check for mispricing before confirming resolution rules.

Instructions

Search both venues and pair markets that appear to ask the same question.

price_gap = Polymarket mid minus Kalshi mid. Pairs must share the question's key words and agree on dates, place, stage, thresholds, direction and negation, and close at similar times, but they are still candidates: always confirm the resolution rules match before acting on a gap.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "compare_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
min_similarityNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the rest and does so well: it defines the price_gap sign convention, lists the matching criteria (key words, dates, place, stage, thresholds, direction, negation, close times), and warns that pairs are unverified candidates. The main missing behavior is what happens when no pair clears the similarity threshold.

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?

Front-loaded with the action, then the metric definition, then matching criteria, then the caution. Dense but every sentence carries information; only the parenthetical list of match dimensions runs long.

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?

An output schema exists, so return values need not be described, and the pairing/threshold semantics are covered. However, for a 3-parameter tool with zero schema documentation, leaving min_similarity and limit unexplained is a real gap that an agent cannot resolve from structured fields.

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

Parameters2/5

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

Schema description coverage is 0%, so the description should compensate and does not. 'query' is loosely implied by 'share the question's key words,' but 'limit' and especially 'min_similarity' – a threshold that directly governs how many pairs come back – are never explained anywhere in the definition.

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 and resource: 'Search both venues and pair markets that appear to ask the same question.' The pairing behavior and the derived 'price_gap = Polymarket mid minus Kalshi mid' make the output concrete and distinguish it from a plain search, though it never names the sibling (search_markets) it supersedes.

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?

Gives real guidance on how to interpret and act on results: pairs are 'still candidates' and you should 'always confirm the resolution rules match before acting on a gap.' That is usage guidance for the output, not for tool selection – there is no explicit when-to-use versus search_markets/get_market.

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