Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__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": "nplg-catalog__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

B3.2/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 behavioral burden, and it does disclose real substance: exclusions (unsettled on a side, 50-50), a minimum-sample rule (rate withheld under 30 paired windows), Wilson 95% intervals, and directional split reporting. However, the final sentence is truncated ('A HEADLINE RATE IS '), which likely removes a needed caveat about interpreting the headline number, and nothing is said about output shape, cost, or data freshness beyond the archive start dates.

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

Conciseness2/5

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

The core definition is front-loaded, which is good, but the text ends in an incomplete sentence fragment ('A HEADLINE RATE IS '), signaling truncation and leaving dead weight. The single dense run-on paragraph mixes purpose, output enumeration, and methodology without structure.

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?

With no output schema and no annotations, the description must cover both behavior and returns; it does enumerate the per-pair fields (paired windows, divergent count, rate with interval, direction, exclusions), which is substantial. But the truncated ending and the absence of any stated response envelope or interpretation caveat leave the definition incomplete for a statistics tool whose headline number is easy to misread.

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%, so both `days` (1-90, default 30, archive start caps) and `asset` (btc/eth/sol/xrp/bnb with per-venue availability) are already fully documented in the schema. The description adds no parameter-specific meaning beyond that, so the baseline of 3 applies.

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 opens with a specific, measurable purpose: how often two venues settled the same 15-minute crypto window differently across all settled windows. It names the concrete venues and price feeds being compared (polymarket.com/Chainlink TWAP vs Kalshi and Polymarket US/CF Benchmarks BRTI), so an agent knows exactly what the tool measures. It loses a point only because the trailing sentence is cut off mid-thought, leaving the headline framing 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 mention of 'same-feed control' signals this is a cross-venue consistency check, and the enumeration of per-pair outputs tells the agent what it can ask for. There is no explicit when-to-use, when-not-to-use, or named alternative tool, so selection still requires inference.

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.