Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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 burden and does reasonably well: it discloses the typical 2-25pp magnitude, states that equivalence of bet shapes is checked and reported, and tells the agent to inspect resolution.topic_matched_by to distinguish curated pairings from keyword guesses. It omits confirmation that this is a read-only comparison and says nothing about freshness or latency of the venue prices.

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 purpose and the equivalence caveat are front-loaded and earn their place, but the text terminates mid-enumeration at '(1) `topic`, 11 pre-mapped macro subjects...' and never supplies mode (2). The dangling structure labeled 'TWO MODES' actively misleads an agent expecting a second mode description to follow.

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 the description partially compensates by pointing at resolution.topic_matched_by and the equivalence verdict. But it announces two modes and documents only one, leaving the explicit-ticker explicit-slug path to be inferred from the schema alone; for a cross-venue comparison tool the return payload is under-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%, so the schema already documents all three parameters including the canonical topic keys, alias behavior, and the override precedence of kalshi_event_ticker and polymarket_event_slug. The description mostly restates those keys, and its one genuinely additive routing note (15-minute crypto windows belong to updown_venue_compare) is also present in the schema text. Baseline 3 applies.

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 specific verb and resource: a cross-venue spread between Kalshi and Polymarket for the same resolving question, and explains why that spread exists (differing participant pools). It is clear what gets computed, but the promise of 'TWO MODES' is only half-delivered, so the full scope of the operation never lands.

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 gives a useful qualifying rule — the delta is a real signal only when bet shapes are equivalent, and the tool flags when they aren't — which is genuine usage guidance. However there is no explicit when-to-use/when-not-to-use framing, no guidance on choosing topic mode versus explicit ticker/slug mode, and the second mode is never described at all.

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.