Skip to main content
Glama

NS Pros MCP Gateway

nist-fluid-properties__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": "nist-fluid-properties__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.7/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 disclosure burden and does well: it states the settlement clause is returned verbatim, that market_prob is a mid price, that both sides are scored at 12:00Z before the high and before resolution, and why (a settled market prices the known outcome at close). Missing are auth requirements, rate limits, and failure behavior beyond the city-mapping fallback.

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 mode split is front-loaded and useful, but the final sentence is cut off mid-token ('brier_market vs brier_'), leaving a dangling, unusable fragment. The LIVE-mode sentence also packs output-field names into a purpose statement, blurring what the tool does with what it returns.

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 explain returns, and it does for LIVE mode (market_prob mid, forecast_prob, edge_pp, verbatim settlement clause) but the BACKTEST return explanation is truncated, so an agent cannot learn what brier_forecast vs brier_market actually represents. The omitted tail also leaves the mode's output shape ambiguous.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents city, date, market_type, backtest_days, and series_ticker with defaults and semantics. The description mostly restates the mode behavior already captured in the `backtest_days` schema text; the output-field names (market_prob, forecast_prob, edge_pp) are return values, not parameters, so they add no parameter meaning.

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 names a specific verb and resource: pricing Kalshi daily high-temperature markets against the NWS forecast for the market's own settlement station, and it explicitly splits into LIVE and BACKTEST modes. It is very clear what the tool does, but it never names a sibling such as polymarket_edge_tracker or polymarket_kalshi_spread, so the agent gets no explicit routing signal against alternatives.

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 clearly: LIVE is the default, and `backtest_days: N` switches to archived-forecast scoring. The precipitation caveat ('return prices but no forecast_prob yet') and the unmapped-city fallback to known_cities[] give real usage context. It stops short of saying when NOT to use it or pointing at sibling pricing tools.

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.