Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__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": "noaa-ncei__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 does substantial work: it discloses that rates are withheld under 30 paired windows (Wilson interval), enumerates exclusions (a side unsettled, 50-50 outcomes), and explains that the Kalshi-to-Polymarket-US pair functions as a same-feed control. It omits any statement about cost, latency, or non-mutation guarantees, but read-only intent is implicit in a statistics tool.

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 and front-loaded with the core comparison before the per-pair breakdown, with no filler sentences. However, the description ends mid-sentence at 'A HEADLINE RATE IS ', which is a visible structural defect and leaves an unfinished caveat hanging in the text.

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?

For a no-output-schema tool it compensates well, enumerating the return fields per pair (paired window count, divergent count, rate with 95% Wilson interval, split direction, exclusions). What is missing is the truncated interpretive caveat and any explicit routing guidance, but the analytic contract is otherwise clear enough to invoke correctly.

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 coverage is 100%, so both parameters are already fully documented, including defaults, allowed assets, per-venue availability, and archive start dates. The description adds no parameter-level meaning beyond the schema, which is the expected baseline 3 when the schema does the heavy lifting.

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?

States a precise verb and resource: measures how often two venues settled the same 15-minute crypto window differently, scoped to every settled window on record. It names the exact venue pairs compared (polymarket.com Chainlink TWAP vs Kalshi, vs Polymarket US BRTI, plus Kalshi-vs-Polymarket-US as a same-feed control), so an agent knows the exact analysis performed without opening the schema.

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 phrasing 'over every settled window on record' and by the schema's look-back/asset notes, but there is no explicit when-to-use or when-not guidance and no named alternative tool. The trailing fragment 'A HEADLINE RATE IS ' appears to have been the start of a caution about interpreting the rate, and its truncation removes what may have been the most actionable 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.