Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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.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 per-strike output fields (market_prob mid, forecast_prob, edge_pp), that the settlement clause is returned verbatim, that unmapped cities return known_cities[] instead of a wrong series, and that scoring happens at 12:00Z before resolution to avoid lookahead bias. It does not mention rate limits, auth requirements, or latency, and the return enumeration is cut off mid-token ('brier_market vs brier_').

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?

The description is front-loaded and dense: capability first, then mode-by-mode output contract. Every sentence carries information, and the LIVE/BACKTEST labels make it scannable. It loses a point for the truncated final clause ('brier_'), which leaves a sentence visibly 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?

There is no output schema, so the description is the only source of return-value information, and it does name the key per-strike fields and the backtest metrics. Combined with the fail-safe behavior for unmapped cities and the scoring-time caveat, an agent can call this correctly and interpret the result. The incomplete trailing clause about the backtest comparison is the one real gap.

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 baseline is 3; the description earns above that by framing `backtest_days` as a mode switch that changes the entire response shape rather than as one more filter, which the schema does not make explicit. It also reinforces that `city` is a constrained vocabulary that fails safe to known_cities[]. Nothing is added for `date` or `series_ticker` beyond what the schema already states.

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?

The first sentence states a precise verb and resource: prices Kalshi daily high-temperature markets against the NWS forecast for the market's own settlement station, and measures whether the forecast beats the market. It immediately names the two operating modes (LIVE default, BACKTEST), so an agent knows the tool's scope and outputs without opening the schema. The sibling list offers no functionally distinct alternative to disambiguate against, so nothing more is owed here.

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?

Mode selection is stated explicitly: LIVE is the default for pricing one city/date, and BACKTEST is triggered by passing `backtest_days: N` for archived scoring over settled days. The schema additionally documents the max of 60 days and the 12:00Z scoring cutoff. What is missing is any explicit when-not-to-use guidance or a statement about which mode answers which kind of question.

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.