Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose useful behavior: the equivalence caveat, the fact that the tool flags non-equivalent bet shapes, and (via the topic param) that resolution.topic_matched_by distinguishes curated pairings from keyword guesses. It says nothing about error handling, rate limits, or what happens when a topic maps to no event, and it leaves mode 2 undefined.

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 writing is dense and reasonably front-loaded, but the text is cut off mid-sentence after mode 1, leaving an announced second mode undelivered. Announcing 'TWO MODES' and then trailing off is a structural defect, not just a length issue.

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?

There is no output schema and no annotations, so the description is the only place return semantics can be explained, and it does point at resolution.topic_matched_by values. But the promised second mode is never written out, and the reader must infer from the schema that mode 2 is the explicit kalshi_event_ticker/polymarket_event_slug path.

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 aliases, canonical keys, and the two explicit-ticker override parameters; baseline 3 applies. The description restates the same eleven pre-mapped topics rather than adding new meaning such as override precedence or what the spread output fields contain.

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 first sentence names a specific verb and resource: a cross-venue spread between Kalshi and Polymarket for the same resolving question, and it explains why that spread exists (2-25pp from differing participant pools). The 'TWO MODES' framing advertises a second operating path that is never actually described, so an agent gets a clear headline purpose but an incomplete picture of how it can be invoked.

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 gives interpretation guidance - when bet shapes are equivalent the delta is a real signal, and the tool self-reports when they aren't - which helps an agent decide whether to trust the output. It never states plainly when to reach for this tool versus alternatives, and the only routing exclusion (15m crypto windows answered by updown_venue_compare) sits in the schema property text rather than the description body.

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.