Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__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": "noaa-ncei__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

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the shape-equivalence caveat, states that the tool self-reports when shapes are not comparable, and explains the confidence semantics of resolution.topic_matched_by ("exact"/"alias" = curated pairing, "phrase"/"token" = keyword guess). It stops short of describing the response shape or failure behavior when no event matches.

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 two sentences are front-loaded and earn their place, but the structure breaks down at "TWO MODES: (1) `topic`..." — mode (2) is never delivered, leaving a dangling enumeration, and the topic key list duplicates the schema. Roughly a third of the text is redundant or incomplete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is judged too generously by the score above: the description announces two modes but only documents one, and with all three parameters optional it never states what the tool does when the agent supplies no topic and no explicit ticker/slug. For a tool with no output schema and no annotations, that is a substantive gap.

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 both override parameters. The description largely restates the canonical key list (fred/btc/eth/cpi... already in the schema) rather than adding new meaning, so the baseline 3 applies even though it is not wrong.

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 first sentence names a specific resource and computation — cross-venue spread between Kalshi and Polymarket on the same resolving question — and the second explains why such a spread exists (differing participant pools, 2-25pp). It also routes the 15-minute crypto windows away to updown_venue_compare, so an agent can tell which tool handles which case.

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 a real usage condition: the delta is only a signal when the bet shapes are equivalent, and it names an explicit alternative (updown_venue_compare) for the btc_15m/eth_15m/sol_15m/xrp_15m/bnb_15m windows. What is missing is guidance on when to supply explicit kalshi_event_ticker/polymarket_event_slug over a topic, and what happens when neither is given.

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.