Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose real behavioral traits: the 2-25pp typical divergence, the caveat that the delta is only signal when the bet shapes are equivalent, and that the tool self-reports when they are not. It also surfaces a confidence field (resolution.topic_matched_by distinguishing curated pairings from keyword guesses). It stops short of describing failure modes, empty results, or latency/data-freshness behavior.

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 lead is front-loaded and the rationale for why the spread matters earns its place, but the structured 'TWO MODES' enumeration is left dangling mid-sentence after item (1), which makes the whole passage feel truncated rather than tight. The long canonical-key roster inside the description duplicates the schema and adds bulk.

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?

With no annotations and no output schema, the description has to carry everything, and it covers purpose, the divergence rationale, and one response field. But it announces two modes and delivers one, never explains the return shape beyond topic_matched_by, and says nothing about behavior when no matching event exists on either venue. Adequate to start a topic-based call, insufficient for the override path or edge cases.

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 baseline is 3, and the description largely restates the topic key list and alias behavior that the schema already documents verbatim. It does add the useful interpretation of resolution.topic_matched_by values (exact/alias vs phrase/token), but that is response interpretation rather than parameter semantics. No net gain over the schema for the three parameters themselves.

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 opening sentence names a concrete verb-resource pair (cross-venue spread between Kalshi and Polymarket for the same resolving question) and explains what the number means. It also implicitly distinguishes itself from updown_venue_compare by routing 15-minute crypto windows elsewhere. What holds it back is the incomplete framing: it promises TWO MODES but only one is described, so the full scope of the tool is never stated.

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 clearly explains when the topic path applies (11 pre-mapped macro subjects) and explicitly redirects 15-minute crypto windows to updown_venue_compare, which is genuine routing guidance. However, it never says when to prefer the explicit kalshi_event_ticker or polymarket_event_slug overrides, and the second mode is missing entirely, leaving the agent to guess a major usage branch.

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.