Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__prediction_calibration

REALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee, read from our own settled-outcomes archive, not from live prices. Answers the one question no venue will: "a side shown at 82 with five minutes left, how often did it ACTUALLY win?" Returns a grid of (price bucket x minute elapsed) -> n, realized_win_rate_pp, mean_shown_price_pp, calibration_gap_pp (realized minus shown, zero means the book is calibrated), breakeven_win_rate_pp (the s

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": {
      "asset": "btc",
      "venue": "polymarket",
      "minute": 5,
      "horizon": "15m"
    },
    "name": "ntsb-investigations__prediction_calibration"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNobtc (default) | eth | sol | xrp | bnb. Coverage differs by venue: polymarket and polymarket-us carry btc/eth/sol/xrp, Kalshi carries btc/eth/bnb.
venueNopolymarket | polymarket-us | kalshi | all (default polymarket). "all" returns one grid per venue, never a merged one.
minuteNoMinutes elapsed since window open, 0-based. Omit for the full grid; pass 5 for the "five minutes in" row only, which is also the cheapest query.
horizonNo15m (default). 5m | 1h | 1d are accepted but only 15m is collected today, so another value returns coverage.windows_total 0 rather than an error.
bucket_ppNoPrice-bucket width in percentage points: 5 | 10 (default) | 20 | 25 | 50. Must divide 100, so the last bucket is never narrower than the rest.
side_conventionNo"favorite" (default) folds each window onto whichever side was the favorite, the frame published claims about early favorites use. "yes" keeps the venue own YES/Up side.

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?

No annotations are supplied, so the description carries the full burden, and it discloses meaningful behavior: results are net of taker fee, derived from settled outcomes rather than live prices, and 'all' for venue returns one grid per venue, never a merged one. It does not cover access requirements, latency, result-size limits, or how thinly populated buckets are handled, which keeps it short of a 5.

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 core scope and provenance are front-loaded, which is good, but the text is a single dense run-on heavy with jargon and a rhetorical flourish ('the one question no venue will'), and it terminates mid-word at '(the s', leaving the breakeven_win_rate_pp explanation unfinished.

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 correctly takes on the job of naming the returned grid fields (n, realized_win_rate_pp, mean_shown_price_pp, calibration_gap_pp, breakeven_win_rate_pp) and explains how to read calibration_gap_pp as zero meaning a calibrated book. The truncation cuts off the last field's meaning, which is the only substantive gap for a 6-parameter read-only analytics tool.

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 the schema already explains asset coverage per venue, venue defaults, the 0-based minute, horizon coverage limits, bucket widths, and side_convention. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

Names a specific measured quantity (realized win rate), specific dimensions (shown price bucket x minutes elapsed), a specific asset class (short-horizon crypto up/down markets), and an explicit provenance (own settled-outcomes archive, not live prices). The agent can immediately tell this apart from any live-quote or price-fetch tool.

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?

The framing 'Answers the one question no venue will: a side shown at 82 with five minutes left, how often did it ACTUALLY win?' gives a strong situational cue, and 'not from live prices' implicitly excludes live-price use cases. However, no alternative tool is named, no when-not-to-use condition is stated, and the agent must infer that this is for historical calibration analysis rather than forecasting.

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.