Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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.7/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 lists the per-pair outputs (paired windows, divergent count, rate, Wilson interval, split direction, exclusions), discloses that the 95% interval is withheld under 30 paired windows, and names the excluded categories (unsettled on a side, 50-50). The only shortfall is the truncated final clause, which appears to have been carrying an additional caveat about the headline rate.

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 substantive content is dense and front-loaded with no filler, but the definition ends mid-sentence ('A HEADLINE RATE IS '), leaving a dangling fragment that breaks the structure and signals lost content. A reader cannot tell whether the missing clause was a caveat, a definition, or a warning.

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?

There is no output schema, so the description must explain return values — and it does, naming the per-pair fields and the withholding and exclusion rules. However, the truncated ending almost certainly contained a material qualification about how to interpret the headline rate, which for a statistics tool is exactly the kind of guidance an agent needs.

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% and the schema already explains the 1-90 day range, the archive start dates per venue, and per-asset venue availability. The description adds no parameter meaning beyond that, so the baseline 3 applies rather than anything higher.

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: it measures how often two venues settled the same 15-minute crypto window differently, and it enumerates the exact venue/feed pairs compared (polymarket.com Chainlink TWAP vs Kalshi and Polymarket US on CF Benchmarks BRTI, plus the same-feed control). An agent can tell exactly what question this tool answers without opening anything else.

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 framing — this is the cross-venue settlement-disagreement measurement — but there is no explicit when-to-use, when-not, or named alternative. The schema hints at scoping (default btc, 30 days), which is helpful but not the same as routing 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.