Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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 burden and mostly meets it: it discloses the returned fields per strike, that the settlement clause is quoted verbatim, the 60-day cap on backtesting, and the non-obvious scoring convention of pricing both sides at 12:00Z on each event day with the rationale given. It also warns that unmapped cities return known_cities[] rather than a wrong series, which is genuine failure-mode disclosure. The one real gap is the truncated final sentence, which leaves the backtest's comparison output only half-described.

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 content is front-loaded and the mode distinction appears in sentence two, which is good ordering. However, the description is one dense block with no separation between the two modes, and the final clause cuts off mid-word ("brier_market vs brier_"), leaving an obviously incomplete sentence that weakens the whole.

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 must describe returns, and it does: market_prob as mid, forecast_prob, edge_pp per strike, verbatim settlement clause, and brier_market vs brier_forecast with per-day detail for backtests. It also flags that precip markets return prices but no forecast_prob yet. The truncated ending and the absence of any note on response size or pagination for a full strike ladder keep it from a 5.

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% and the schema text is already rich, so the baseline is 3. The description adds the mode framing that explains why `backtest_days` exists and what it overrides, but most parameter detail (city list, date format, market_type enum, series_ticker examples) is restated from the schema rather than extended. Meaningful but largely duplicative.

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 opening sentence names a specific verb and resource — pricing Kalshi daily high-temperature markets against the NWS forecast for the market's own settlement station, including the edge measurement. The two modes (LIVE vs BACKTEST) are named and distinguished, so an agent knows exactly what class of operation it is invoking. This is well beyond a restatement of the name.

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 states that LIVE is the default and that supplying `backtest_days: N` switches to measurement mode "instead of pricing today," which is an explicit selection rule between the two behaviors. What it lacks is guidance on when the surrounding siblings (e.g. polymarket_edge_tracker, polymarket_kalshi_spread) should be preferred, and it gives no precondition notes such as credential or subscription 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.