Skip to main content
Glama

NS Pros MCP Gateway

nist-standards__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": "nist-standards__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 supplied, the description carries the full burden and does substantial work: it discloses statistical treatment (95% Wilson interval), a suppression rule (withheld under 30 paired windows), an explicit exclusion taxonomy (unsettled on a side, 50-50), and the per-pair breakdown. It falls short of a 5 because the final clause — 'A HEADLINE RATE IS ' — is truncated, leaving the aggregation/headline behavior and any caveats about interpreting it unstated.

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 first sentence is front-loaded and information-dense, which is good, but the body is a single sprawling sentence and the text terminates mid-clause ('A HEADLINE RATE IS '), an obvious truncation that undercuts structure. The content that survives earns its place; the packaging does not.

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?

With no output schema, the description takes on the return-value burden and largely meets it: it enumerates the per-pair fields (paired windows, divergent count, rate plus Wilson interval, split direction, exclusions). It is not fully complete because the cut-off sentence about the headline rate leaves the top-level summary output and its interpretation undefined.

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 itself documents the days range (1-90, default 30), the archive start dates, and the per-asset venue coverage in more detail than the description does. The description adds no parameter-level meaning of its own, 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 description opens with a precise, testable statement of what is measured: how often two venues settled the SAME 15-minute crypto window differently, across every settled window on record. It then names the three exact venue/feed pairings (polymarket.com Chainlink TWAP, Kalshi and Polymarket US on CF Benchmarks BRTI) and identifies the Kalshi/Poly- US pairing as a same-feed control, which goes well beyond restating the tool name.

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 rather than stated: the reader infers this is the cross-venue agreement measure and that same-feed pairs serve as a control. There is no explicit when-to-use versus when-not, and no named alternative tool or precondition (e.g. minimum window count for a trustworthy headline) beyond the parenthetical about withholding under 30 paired windows.

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.