Skip to main content
Glama

NS Pros MCP Gateway

numverify__polymarket_kalshi_spread

Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ, when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says so. TWO MODES: (1) topic, 11 pre-mapped macro subjects ("fed", "btc", "eth", "cpi", "gdp", "sp500", "recession", "next_pope", "next_uk_pm", "next_israel_pm", "2028_president") auto-fetch the matching event on each venue.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "fed"
    },
    "name": "numverify__polymarket_kalshi_spread"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoSubject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president, plus the 15-minute crypto up/down windows btc_15m | eth_15m | sol_15m | xrp_15m | bnb_15m ("btc 15m", "bitcoin 15 minute"), which are answered by updown_venue_compare for the window in progress, but aliases and keywords resolve too ("bitcoin", "fed rate decision", "ethereum", "inflation", "s&p 500", "us recession", "next pope", "2028 election"). Check resolution.topic_matched_by in the response: "exact"/"alias" is a curated pairing, "phrase"/"token" is a keyword guess.
kalshi_event_tickerNoExplicit Kalshi event ticker, e.g. "KXFED-26OCT". Overrides the topic-mapped Kalshi side.
polymarket_event_slugNoExplicit Polymarket event slug, e.g. "fed-decision-in-june-825". Overrides the topic-mapped Polymarket side.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does meaningful work: it explains that the same outcome can price 2-25pp apart due to differing participant pools, that the tool itself flags non-equivalent bet shapes, and that resolution.topic_matched_by distinguishes curated pairings from keyword guesses. Missing: any statement that this is a read-only/non-mutating operation and no sense of latency or how many events are fetched per call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening is well front-loaded with the core idea and the differentiation rationale, but the enumeration 'TWO MODES: (1) `topic` ...' is cut off and never delivers mode (2), leaving a dangling list that the reader must reconstruct from the schema. The mid-sentence run-on about participant pools could be tightened.

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?

For a three-parameter tool with no annotations and no output schema, the description should explain the returned shape and what the second mode is. It partially compensates by referencing resolution.topic_matched_by and the equivalence self-check, but the promised second mode is absent and the spread output format (direction, pp magnitude, confidence) is left unexplained.

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 documents topic keys, aliases, and the two override parameters. The description adds only marginal meaning beyond that — the pre-mapped subject list is repeated from the schema, and the override behavior ('Overrides the topic-mapped Kalshi side') is already spelled out in the schema descriptions. Baseline 3 is appropriate.

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?

States a specific verb+resource: a cross-venue spread between Kalshi and Polymarket on the same resolving question. The framing ('the same resolving question', 'when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says so') makes it unambiguous what the output means and how it differs from a single-venue price tool.

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?

Gives a concrete routing rule: the 15-minute crypto up/down windows (btc_15m, eth_15m, etc.) 'are answered by updown_venue_compare for the window in progress', which is an explicit alternative-tool handoff. It also tells the agent how to pick a topic versus supply explicit tickers/slugs. It stops short of stating when a spread comparison is pointless (e.g., non-equivalent resolution criteria) beyond the tool's own self-check.

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.