Skip to main content
Glama

NS Pros MCP Gateway

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

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does well on outputs (market_prob, forecast_prob, edge_pp per strike, settlement clause verbatim) and on backtest methodology (both sides scored at 12:00Z before the daily high), but the final sentence is cut off mid-word at 'brier_market vs brier_', leaving the backtest return contract incomplete, and nothing is said about failure modes, cost, or rate limits.

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 description is front-loaded and dense with useful detail, but it ends abruptly mid-token, which is a structural defect rather than concision. Undefined shorthand like 'edge_pp' and 'market_prob (mid)' is used without units or interpretation, costing a little clarity in an otherwise efficient passage.

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?

For a five-parameter tool with no annotations and no output schema, the definition covers the LIVE payload reasonably but the truncated tail leaves the BACKTEST return shape (brier comparison, settlement-vs-forecast basis, per-day detail) only partially described. An agent could invoke it correctly, but would be guessing at what the backtest output actually contains.

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, and the description earns above that by explaining that `backtest_days` switches the whole tool into a different measurement mode rather than merely filtering results. It also reinforces that LIVE pricing is scoped to 'one city and settlement date', which clarifies how `city` and `date` interact.

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?

The description opens with a specific verb and resource: pricing Kalshi daily high-temperature markets against the NWS forecast for the market's own settlement station, and it adds the measurement goal. It does not, however, distinguish this from sibling tools that share the identical `kalshi_weather_edge` suffix across other NOAA data sources, so the agent gets no signal about why this source rather than another.

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?

It explicitly lays out two modes and the switch between them: LIVE is the default for pricing one city and date, BACKTEST activates when `backtest_days: N` is supplied to score archived forecasts on settled days. That is clear when-to-use guidance for the two paths, but there are no exclusions or pointers to alternative tools for adjacent needs.

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.