Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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.3/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 substantial work: it discloses the data provenance (own archive, not live prices), that the metric is net of taker fee, and the exact grid shape and column meanings, including that calibration_gap_pp of zero means the book is calibrated. It stops short of covering auth, latency, or freshness caveats, and the final sentence is cut off mid-clause, leaving breakeven_win_rate_pp unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core resource and scope, then the output shape. The rhetorical framing ('the one question no venue will') costs a sentence but does convey why the metric matters, so it mostly earns its place. The trailing truncation is a structural defect that leaves the last column's definition incomplete.

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 all-optional parameters with full schema documentation plus an enumerated return-field list make this callable without guessing, and the 'all' vs single-venue grid behavior is addressed. What is missing is minor: the cut-off breakeven definition and any note on data freshness or coverage limits beyond what the schema states.

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% with rich per-parameter descriptions, so the baseline is 3; the description adds genuine meaning by explaining what the returned cells are and how bucket_pp and minute interact to form the grid axes. It does not restate defaults or enum values, correctly leaving that to the schema.

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 specific metric (realized win rate), the exact conditioning dimensions (shown price bucket x minutes elapsed), the market class (short-horizon crypto up/down), and the data source (own settled-outcomes archive). The contrast 'not from live prices' disambiguates it from any live-quote tool, and the concrete example question makes the semantics unmistakable.

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 description makes clear this is a post-hoc calibration lookup over settled outcomes rather than a live pricing tool, which effectively tells the agent when to reach for it. It does not name a specific alternative tool or state an explicit 'do not use for X' exclusion, and the 'cheapest query' hint lives in the schema rather than here.

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.