Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__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": "nplg-catalog__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?

With no annotations, the description carries the full load and does meaningful work: it explains that 2-25pp gaps arise from differing participant pools, that equivalence is validated and reported, and that response field resolution.topic_matched_by encodes confidence ("exact"/"alias" = curated, "phrase"/"token" = keyword guess). It omits failure behavior when no event matches, rate limits, and the rest of the response shape.

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 core concept is front-loaded in the first sentence and the equivalence caveat is well placed. But the description ends mid-thought after "TWO MODES: (1) `topic` … auto-fetch the matching event on each venue.", leaving a promised second mode undelivered and making the structure feel truncated rather than tight.

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-optional-parameter matching tool with no annotations and no output schema, the definition conveys the concept, ambiguity handling, and mode 1 adequately, and the schema documents all parameters. It falls short of complete because mode 2 is unstated, the response contents beyond topic_matched_by are unknown, and no-match/no-data behavior is never described.

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 coverage is 100% and the topic description already enumerates canonical keys, 15-minute windows, alias resolution, and the topic_matched_by confidence values, so the description largely restates structured data. The one genuinely additive note — which values are curated pairings versus keyword guesses — also appears in the schema, leaving this at the baseline.

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?

"Cross-venue spread between Kalshi and Polymarket for the same resolving question" states the exact resource and the analytical output (a price delta), which is more specific than a name restatement. It also names updown_venue_compare as the handler for 15-minute crypto windows, giving partial sibling differentiation, though it does not distinguish itself from the other listed polymarket_* analytics tools.

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 frames the core judgment call well: a delta is a signal only when bet shapes are equivalent, and the tool reports when they aren't. However, the "TWO MODES" framing is introduced and then only mode (1) `topic` is described — mode (2) is never stated, so an agent cannot tell from the description when to skip the topic keyword and supply raw tickers/slugs instead.

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.