Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__kalshi_weather_edge

Prices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market. Two modes. LIVE (default): returns the full strike ladder for one city and settlement date with market_prob (mid), forecast_prob, and edge_pp per strike, plus the settlement clause verbatim. BACKTEST (backtest_days: N): scores an archived gridded forecast against the market on settled days and returns brier_market vs brier_

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": {
      "city": "nyc"
    },
    "name": "npi-registry__kalshi_weather_edge"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity to price, e.g. "nyc", "chicago", "los angeles", "miami", "austin", "houston", "denver", "philadelphia". Defaults to nyc. Unmapped cities return known_cities[] rather than a wrong series.
dateNoSettlement date as YYYY-MM-DD. Defaults to the soonest open event. Daily weather markets open ~1-2 days ahead and close 05:00Z the next day.
market_typeNo"high_temp" (default) | "precip". Precipitation markets return prices but no forecast_prob yet.
backtest_daysNoRun measurement mode over the last N settled days (max 60) instead of pricing today. Returns brier_market vs brier_forecast, the settlement-vs-forecast basis, and per-day detail. Both sides are scored at 12:00Z on each event day, before the daily high and before resolution, because a settled market prices the known outcome at close.
series_tickerNoExplicit Kalshi series, e.g. "KXHIGHNY" or "KXHIGHTBOS" (Boston). Overrides `city`; use it for any of the 121 daily weather series not in the city list.

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 so well: it discloses the return payload per mode (market_prob mid, forecast_prob, edge_pp per strike, verbatim settlement clause), the Brier-score comparison in backtest mode, and the scoring-at-12:00Z rationale for avoiding lookahead. It does not state read-only/network/side-effect posture explicitly, but the analysis semantics are unusually well disclosed.

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 and dense -- mode names are capitalized and the live-mode return fields are enumerated in one clause. However, the final sentence is cut off mid-token ("brier_market vs brier_"), which is a real structural defect in an otherwise tight description.

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 fully explain return values, and it does for LIVE mode but truncates exactly where the BACKTEST return fields are being enumerated. For a two-mode analytical tool with five parameters, the truncated tail leaves the backtest output contract incomplete.

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 100%, so the schema already documents each parameter. The description nevertheless adds meaning the schema cannot: that `backtest_days` is a mode switch that changes the entire return shape rather than a filter, and that the two modes answer different questions. That is genuine added semantics above the baseline 3.

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 verb and resource -- pricing Kalshi daily high-temperature markets against the NWS forecast for the market's own settlement station -- and adds the analytical claim (whether the forecast beats the market). That framing distinguishes it from sibling tools like polymarket_edge_tracker and polymarket_kalshi_spread without needing their schemas.

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 two modes are explicitly gated: LIVE is the default, and BACKTEST is selected by supplying `backtest_days: N`. That is a clear use-case selector. What's missing is any statement of when to reach for this tool versus the sibling edge/spread tools, so the guidance is internally clear but externally silent.

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.