Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__updown_divergence_rate

How often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair: windows both venues settled, divergent count, the rate with its 95% Wilson interval (withheld under 30 paired windows), which direction they split, and what was excluded (unsettled on a side, 50-50). A HEADLINE RATE IS

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": {
      "days": 30,
      "asset": "btc"
    },
    "name": "nj-mvc__updown_divergence_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back in days, 1-90 (default 30). The archive starts 2026-09-22 (polymarket.com, Kalshi) and 2026-10-07 (Polymarket US, btc), so a longer span is capped by what is held; coverage is reported per pair.
assetNobtc (default) | eth | sol | xrp | bnb. The archive holds btc/eth on all three venues, sol/xrp on polymarket.com and Polymarket US, bnb on Kalshi only (no pair).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 largely meets it: it discloses that intervals are withheld under 30 paired windows, that unsettled-side and 50-50 windows are excluded, that coverage varies per pair, and that the archive start dates differ by venue. It does not cover read-only/non-mutating nature explicitly or any cost/rate constraints, keeping it below a 5.

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 body is dense but front-loaded and earns its detail on return-value semantics. However the description ends mid-sentence with the fragment 'A HEADLINE RATE IS ', which is truncated text rather than a sentence, leaving a dangling clause and an unclear warning.

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

Completeness4/5

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

No output schema exists, so the description must explain the response, and it does: per-pair paired-window counts, divergence counts, rate with 95% Wilson interval, split direction, and exclusions. The only real gap is the truncated final clause, which was presumably a caveat about interpreting the headline rate.

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%, and the schema already documents days (1-90, default 30, archive start dates) and asset (venue-by-venue availability). The description adds essentially no parameter meaning beyond that, so the baseline 3 applies.

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 opening sentence gives a specific computation over a specific resource ('how often two venues settled the SAME 15-minute crypto window differently, over every settled window'), and it names the exact venue/feed pairs being compared. An agent knows precisely what number this tool produces and why the Kalshi-vs-Polymarket-US pair exists as a control.

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?

Usage is only implied: the description makes clear this is a cross-venue agreement/drift analysis, but never states when to reach for it versus a plain price or settlement tool, nor any exclusion such as 'do not use for per-window inspection'. The 'same-feed control' framing does help interpretation, but there is no explicit when-to-use or when-not guidance.

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.