Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__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": "nplg-catalog__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/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 behavioral burden and does substantial work: it names the returned fields (market_prob as mid, forecast_prob, edge_pp, settlement clause verbatim), discloses that precip markets return prices but no forecast_prob, that unmapped cities return known_cities[] rather than a wrong series, the 60-day cap, and the 12:00Z scoring convention. It omits auth/rate-limit context and the final backtest sentence is cut off mid-word ('brier_'), leaving the measurement output incompletely described.

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 with the purpose, then cleanly partitioned into LIVE and BACKTEST blocks with no filler. The one real defect is that the prose terminates mid-token at 'brier_', signaling truncation of the backtest return description.

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?

For a 5-parameter, no-annotation, no-output-schema tool, the description covers defaults, mode selection, return fields, and edge-case fallbacks well. The truncated backtest return description is the main hole an agent would notice, though the schema's own `backtest_days` text partially backfills it.

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 would be 3, but the description adds a layer the schema does not: it frames `backtest_days` as a wholesale mode switch rather than an ordinary filter, and explains that the backtest scores both sides at 12:00Z before resolution so a settled market prices the known outcome at close. That reasoning about parameter interaction is genuine value beyond the field descriptions.

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: 'Prices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station.' The 'OWN settlement station' qualifier and the explicit split into LIVE vs BACKTEST modes make the tool's scope unmistakable. It does not name a sibling (e.g. polymarket_edge_tracker or polymarket_kalshi_spread) to contrast against, so it stops short of a 5.

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?

Provides explicit internal routing: LIVE is the default and BACKTEST is selected by passing `backtest_days: N`, with the consequence of each mode spelled out. It does not address when to choose this tool over the sibling pricing tools, so cross-tool guidance is absent, but within-tool usage is unambiguous.

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.