Skip to main content
Glama

NS Pros MCP Gateway

noirlab-datalab__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": "noirlab-datalab__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.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does well on this front: it discloses that rates are withheld under 30 paired windows, that exclusions (unsettled on a side, 50-50) are reported, and that coverage is reported per pair. However, the description is truncated mid-sentence at 'A HEADLINE RATE IS ', so a key behavioral caveat about interpreting the headline rate is cut off, and there is no statement about cost, latency, or determinism.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope statement is front-loaded and every clause about pairs, per-pair metrics, and exclusions earns its place. The one defect is that the final sentence is cut off mid-thought ('A HEADLINE RATE IS '), leaving an incomplete fragment rather than a finished caveat.

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 must and largely does describe the return shape: paired-window counts, divergent counts, rates with 95% Wilson intervals, split direction, and exclusions. Only the truncated closing caveat and the absence of any guidance on choosing among similar tools keep this from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and both parameters carry rich descriptions in the schema including the default look-back, the 1-90 cap, archive start dates, and per-asset venue availability. The description adds no parameter detail of its own, which is acceptable given the schema's completeness, but it does reinforce the per-pair coverage semantics that govern how `days` plays out.

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 names a specific computation (how often two venues settled the SAME 15-minute crypto window differently) over a specific scope (every settled window on record), and enumerates the exact venue pairs compared, including the same-feed control. This is far more than a restatement of the name and lets an agent know precisely which analysis it produces.

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 context is implied by the described output (divergence rates with Wilson intervals for cross-venue sanity checks), but there is no explicit when-to-use or when-not-to-use guidance, no named alternative tools, and no stated prerequisites. The agent must infer the analytical purpose from the mechanics alone.

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.