Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__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": "noaa-ncei__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

A4.2/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 burden and does much of it: it discloses the data provenance (settled-outcomes archive), that results are net of taker fee, and defines calibration_gap_pp as realized minus shown with the interpretive rule ("zero means the book is calibrated"). It does not mention rate limits, latency, or empty-result behavior beyond what leaks into the schema descriptions.

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?

Leading with the measurement is good front-loading, but the second sentence is a rhetorical question ("Answers the one question no venue will") that spends words on persuasion rather than information. More importantly, the text is truncated mid-clause ("breakeven_win_rate_pp (the s"), so the output-field enumeration — the only documentation of return values, since there is no output schema — is left 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?

For a six-parameter, fully optional, read-only analytical tool with no annotations and no output schema, the description covers source, fee treatment, output columns, and calibration interpretation — enough to call it correctly. The gaps are the cut-off breakeven definition and no guidance on volume/n observability or what an empty grid means.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, which sets a baseline of 3, but the description adds interpretive meaning by framing the grid as (price bucket x minute elapsed) and by phrasing the question as "a side shown at 82 with five minutes left" — making concrete what bucket_pp and minute measure. The truncation cuts off the breakeven_win_rate_pp explanation, so the added meaning is real but incomplete.

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?

"REALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets" names a specific measurement, its two axes, and its domain scope, then sharpens it by stating the source is "our own settled-outcomes archive, not from live prices." An agent can tell exactly what this computes and how it differs from a live-price query without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The explicit "not from live prices" plus the settled-archive framing gives clear context on when this tool applies: historical calibration checks, not current quoting. The worked example ("a side shown at 82 with five minutes left") also models the intended query shape. However, no sibling alternative is named and no when-not condition is stated, so the agent must infer routing.

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.