Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full behavioral burden, and it does disclose meaningful context: the data comes from an internal settled-outcomes archive, is net of taker fee, and is not derived from live prices. It does not cover permissions, cost/latency beyond a hint that a single-minute query is "the cheapest query", pagination, or empty-result behavior, and the return-field explanation is cut off mid-sentence ("breakeven_win_rate_pp (the s"), leaving the behavioral picture incomplete.

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 space is spent on rhetorical framing ("Answers the one question no venue will") and the final clause is truncated mid-definition, so the entry is both padded at the front and incomplete at the back. It is readable but not tight.

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 the result shape; it does list the grid keys (n, realized_win_rate_pp, mean_shown_price_pp, calibration_gap_pp, breakeven_win_rate_pp) and interprets calibration_gap_pp = 0 as a calibrated book. However the breakeven_win_rate_pp definition is truncated, leaving one of five returned fields unexplained for a 6-parameter analytical 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% and each parameter already documents its allowed values, defaults, and quirks (venue coverage by asset, non-15m horizons returning coverage.windows_total 0, bucket_pp needing to divide 100, side_convention semantics). The description adds only a light conceptual frame (price bucket x minute elapsed grid) and does not extend parameter meaning beyond the schema, so the baseline 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?

States a specific verb+resource: realized win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, computed from a settled-outcomes archive rather than live prices. That is concrete and distinguishes it from a live-price/lookup tool, though the sibling names offered here share the same suffix across unrelated domains and the description does not address any of them.

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: it frames the use case as the question venues won't answer ("a side shown at 82 with five minutes left, how often did it ACTUALLY win?") and explicitly excludes live prices as a data source. There is no explicit when-to-use/when-not statement and no named alternative for the live-price or raw-outcomes path.

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.