Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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.7/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 substantial work: it discloses that rates are withheld under 30 paired windows, that direction of the split is reported, and what is excluded (unsettled sides, 50-50 outcomes). It does not state whether this is a read-only computation versus something cached/materialized, and the closing caveat about the headline rate is cut off mid-sentence, leaving the most important interpretation warning unfinished.

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 definition is front-loaded and dense with substantive detail, but it ends with a dangling fragment ('A HEADLINE RATE IS '), which is both wasted text and a sign the description was truncated mid-thought. That leaves an incomplete idea occupying the position where the most important caveat should be.

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 statistical comparison tool with no output schema and no annotations, the description does cover the return shape well (paired-window counts, divergent counts, Wilson interval, direction, exclusions). However, the truncated final sentence removes what appears to be a critical reading caveat about the headline rate, so an agent cannot know the intended interpretation guardrail.

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 explains the days range with archive start dates and the asset enum with per-venue availability. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies — the schema, not the prose, does the work here.

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 measure (how often two venues settled the same 15-minute crypto window differently) plus the comparison set: polymarket.com vs Kalshi, polymarket.com vs Polymarket US, and Kalshi vs Polymarket US as a same-feed control. Naming the three venues also distinguishes this instance from the many sibling *__updown_divergence_rate tools, which key on other data sources.

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 implied by the content — you would call it to quantify cross-venue settlement disagreement — but there is no explicit when-to-use, when-not-to-use, or named alternative. The one genuine routing hint is the 'same-feed control' framing for Kalshi vs Polymarket US, which tells an agent how to interpret that pair rather than when to pick this tool over another.

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.