Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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 load and does so well for a read-only analytics tool: it discloses the per-pair return contents, the statistical method (95% Wilson interval), the deliberate suppression rule under 30 paired windows, directional splits, and an explicit exclusion accounting (unsettled on a side, 50-50). It does not cover auth, rate limits, or response size, but for a computation endpoint the disclosed caveats are the substantive behaviors an agent needs.

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 structure is sound – a one-line thesis followed by a "Per pair:" enumeration of return fields – but the prose is dense, jargon-heavy, and the description terminates mid-sentence, which is a real defect rather than a stylistic quirk. Sentences are doing work, but the truncation undercuts front-loading of the payoff.

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 zero-required-parameter analytics tool with no output schema, the description is close to complete: it explains what is computed, over what universe, per pair, and what is withheld and why. What is missing is the tail of the final sentence and any guidance on interpreting or acting on the headline rate.

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 itself documents both parameters thoroughly, including archive start dates per venue and which assets exist on which venue. The prose adds nothing about days or asset beyond what the schema already says, so the baseline 3 applies rather than a bonus.

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 opening sentence states a specific measurable quantity (how often two venues settled the same 15-minute crypto window differently) and names the exact venue pairs and price feeds, which lets an agent distinguish it from sibling divergence tools. The purpose is unambiguous even though the final sentence is cut off mid-clause ("A HEADLINE RATE IS "), leaving the intended interpretation guidance 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 only implied: an agent can infer this tool answers venue-comparison questions, and the mention of "same-feed control" hints at how to sanity-check results. There is no explicit when-to-use, when-not, or alternative-tool routing, and the truncated closing sentence appears to have been the place those instructions were going.

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.