Skip to main content
Glama

netherlands-tenders__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": "netherlands-tenders__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.1/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 much of it: it discloses that settlement clauses are returned verbatim, that unmapped cities return `known_cities[]` instead of a wrong series, that precipitation markets return no `forecast_prob`, and the 12:00Z scoring convention that avoids look-ahead bias. The final sentence is cut off ('brier_'), leaving the backtest's second metric undefined, which is a real but isolated gap.

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?

The purpose is front-loaded, and the LIVE/BACKTEST labels give the reader a clean scaffold for two distinct behaviors. It is dense but mostly earns its words; the truncated final clause is a structural defect rather than verbosity, and it costs a little clarity at the point where the backtest output is described.

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 five-parameter, all-optional analytical tool with no output schema, the description does the necessary work of naming the returned fields for LIVE mode (mid, forecast_prob, edge_pp, settlement clause). The backtest return description is incomplete due to the cut-off, and there is no mention of latency, data staleness, or failure modes for a market-priced tool where those matter.

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 all five optional parameters in detail, including the city list, date format, and the 60-day backtest cap. The description adds mode-level semantics — that `backtest_days` switches the tool from pricing to measurement — but no format or parsing detail beyond the schema, so the baseline of 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?

The description states a specific verb and resource pair — pricing Kalshi daily high-temperature markets against the NWS forecast for the market's own settlement station — and adds a second measurable goal (whether the forecast beats the market). This is far more specific than the sibling tools with the same name suffix, and an agent can tell exactly what domain of question this answers.

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 clearly separates the two operating modes and states LIVE is the default, and it explains when to reach for `series_ticker` (any of the 121 series not in the city list) and when precipitation markets are appropriate. What's missing is any explicit when-not-to-use or routing to an alternative tool such as the spread or edge trackers, but the in-tool mode guidance is solid.

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.