Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full transparency burden. It does disclose valuable behavior — per-pair outputs, a Wilson 95% interval withheld under 30 paired windows, split direction, and exclusion categories (unsettled on a side, 50-50) — but the definition terminates mid-sentence at 'A HEADLINE RATE IS ', so a caveat about how to read the headline number is lost. It also says nothing about read-only status, cost of scanning the full archive, or response shape beyond the field list.

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 sentence is front-loaded and information-dense with no filler, but the definition literally ends mid-clause ('A HEADLINE RATE IS '), which is a structural defect rather than brevity. A reader cannot tell whether the missing words are a warning, a definition, or a usage rule.

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 tool with no annotations and no output schema, the description does substantial work by enumerating the returned fields and the suppression/exclusion rules. However, the truncated ending removes what appears to be a key interpretive caveat, and nothing is said about archive-scan cost or limits when `days` is large.

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 schema already documents both `days` (1-90, default 30, archive start dates) and `asset` (btc/eth/sol/xrp/bnb with per-venue availability). The description adds only indirect meaning — that coverage is reported per pair and that some assets have no comparable pair — which is a marginal supplement, so the 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 description states a precise computation (how often two venues settled the same 15-minute crypto window differently) and enumerates the three venue pairs being compared, so an agent knows exactly what the tool measures. It stops short of contrasting itself with any alternative, but the resource is specific enough that misuse is unlikely.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named or excluded. The only contextual steering is the implicit 'use this to compare venues' framing plus the per-parameter notes about which assets form valid pairs, which is schema-level information rather than usage 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.