Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__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": "ntsb-investigations__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.6/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 the comparison methodology (Chainlink TWAP vs. CF Benchmarks BRTI), the statistical treatment (95% Wilson interval, withheld under 30 paired windows), the direction-of-split reporting, and the explicit exclusion categories (unsettled on a side, 50-50). These are genuine behavioral facts an agent could not infer from the schema. It falls short of 5 because the response shape is only partially described and the final sentence is truncated.

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 content is dense and largely front-loaded, moving from the core question to the comparison pairs to the per-pair outputs in a logical order. However, it is delivered as a small number of very long clauses, and the dangling 'A HEADLINE RATE IS ' is a structural defect that leaves the reader without the intended closing takeaway.

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?

There is no output schema and no annotations, so the description must describe returns itself — and it does, listing paired-window counts, divergent counts, the rate with confidence interval, split direction, and exclusions per pair. Coverage of the tool's behavior is strong for its complexity. The incomplete final sentence is the only material gap.

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 embedded parameter descriptions are already rich, covering the 1-90 day range, archive start dates per venue, and which assets exist on which venue. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies — the schema, not the prose, does the heavy lifting here.

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 names a specific computation (rate at which two venues settled the same 15-minute crypto window differently) and enumerates the three venue pairs being compared, including which price feeds each uses. An agent can tell exactly what metric this produces. It loses a point only because the final clause is cut off mid-sentence ('A HEADLINE RATE IS '), leaving the framing statement incomplete.

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 description makes clear this is an analytical cross-venue comparison, and the mention of a same-feed control hints at validating divergence against a baseline. But there is no explicit when-to-use guidance, no statement of when to prefer this over a raw settlement-lookup tool, and no note on what a caller should conclude from the control pair. The truncated ending may have contained that guidance, but as supplied it is absent.

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.