Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose useful behavior: the 2-25pp spread range, that it self-reports when the shapes aren't equivalent, and a 'TWO MODES' framing plus the resolution.topic_matched_by field for judging match confidence. But the sentence announcing the two modes is cut off mid-enumeration -- mode (2) is never described -- so the behavioral picture is materially incomplete.

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 sentence is well front-loaded, but the 'TWO MODES: (1)...' enumeration is left dangling with no second item, which is both wasted setup and a structural failure. Some prose ('because their participant pools differ') is explanatory rather than operational, though it does justify the signal interpretation.

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?

This is a comparison tool with no output schema and no annotations, so the description should explain both invocation modes and what comes back. It partially compensates by naming resolution.topic_matched_by, but the missing mode (2) and the absent return-shape description leave an agent guessing at how to supply explicit event identifiers together or how to read the spread output.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, and the description adds real meaning on top: it enumerates the 11 canonical topic keys, lists the alias/keyword forms, and explains the override relationship for the explicit ticker and slug. The truncation leaves the topic-plus-explicit-ticker mode combination under-explained, keeping it below top marks.

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 pairing: a cross-venue spread between Kalshi and Polymarket for the same resolving question, including the substantive rationale (2-25pp divergence from differing participant pools). It is clearly distinct from siblings like polymarket_edges or kalshi_weather_edge. It loses a point because the sentence structure drifts into significance commentary before the tool's operation is fully pinned down.

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?

It conveys the interpretive rule -- when bet shapes are equivalent the delta is a real signal, otherwise the tool flags it -- which is genuine usage guidance for reading output. It also points 15-minute crypto windows at updown_venue_compare (via the schema text). However there is no explicit when-to-use-this-vs-siblings guidance and no stated prerequisites for comparing the venues.

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.