Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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?

With no annotations, the description carries the full load and mostly succeeds: it discloses the taker-fee netting, the settled-archive provenance versus live prices, and the semantics of calibration_gap (realized minus shown, zero means calibrated). It omits anything on query cost or read-only safety, and the trailing sentence defining breakeven_win_rate_pp is cut off mid-word.

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 definition is front-loaded and dense, but it carries a rhetorical detour (“the one question no venue will”) and ends abruptly mid-sentence, leaving a truncated field definition in the most information-dense part of the text.

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?

Six optional parameters with full schema coverage and no output schema mean the description must describe the return shape, and it does: an (price bucket x minute elapsed) grid of n, realized_win_rate_pp, mean_shown_price_pp, calibration_gap_pp, and breakeven_win_rate_pp. The only gap is the truncated final field description.

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 documents every parameter including venue, horizon, bucket_pp, and side_convention. The description only restates the two grid axes (price bucket x minute elapsed) that map to those params, adding little beyond the schema; 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?

States a precise verb and resource: realized win rate by shown price and minutes elapsed for short-horizon crypto up/down markets. It draws a sharp line against the obvious confusion source by saying the data comes from a settled-outcomes archive, not live prices, so an agent can tell it apart from any live-quote 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 description supplies a motivating question (“a side shown at 82 with five minutes left, how often did it ACTUALLY win?”) which implies the when-to-use case, but never states when not to use it or names any alternative tool to prefer. Guidance is implied rather than explicit.

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.