Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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.9/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 enumerates the returned fields (market_prob as mid, forecast_prob, edge_pp, verbatim settlement clause), bounds the backtest at max 60 days, discloses that both sides are scored at 12:00Z before resolution, and notes unmapped cities return known_cities[] rather than a wrong series. It does not say whether the tool is strictly read-only or whether it has rate limits, but nothing contradicts a safe read-only analysis role.

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?

Front-loaded and mode-structured, which is good, but the final clause is cut off mid-sentence ('brier_market vs brier_'), leaving the backtest return signature incomplete. The dense single paragraph also merges two distinct modes rather than separating them.

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, two-mode tool with no output schema and no annotations, the description covers most of what an agent needs: mode selection, key return fields, and the 12:00Z scoring rule. However, the truncated ending leaves the backtest outputs (brier_forecast, settlement-vs-forecast basis, per-day detail) partially unexplained, and return shape for LIVE mode is only listed, not structured.

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 coverage is 100%, so the schema already documents city, date, market_type, backtest_days and series_ticker in detail. The description adds the higher-level framing that backtest_days switches the whole operation into measurement mode, but that framing is largely repeated in the schema's own backtest_days text, so baseline 3 applies.

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?

Names a specific verb+resource ('Prices Kalshi daily high-temperature markets against the NWS forecast'), pins the scope to the market's OWN settlement station, and states the second purpose (measuring whether the forecast beats the market). An agent can tell immediately this is a forecast-vs-market pricing/backtest tool rather than a spread or edge-tracking tool.

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?

Explicitly partitions behavior into two modes and gives the selector for each: LIVE as the default, BACKTEST when 'backtest_days: N' is supplied. That is clear context for choosing between behaviors, though it never states when to prefer this tool over the sibling pricing tools (polymarket_kalshi_spread, polymarket_edge_tracker).

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.