Smarter Weather

Official32 toolsLive

by smarterweather · TypeScript

Smarter Weather MCP: forecasts, alerts, outlooks, observations, AQI, grids, and map imagery.

🛠️ Key Features

MCP server for Model Context Protocol with weather-focused data
Exposes forecasts, alerts, outlooks, observations, AQI, grids, and map imagery
Topics include api, mcp, model-context-protocol, weather-data, and related tooling
Compatibility with standard MCP clients and OpenAPI workflows
Readme excerpt describes stdio-to-HTTP bridge and authentication flow

🚀 Use Cases

Connect local MCP clients (Claude Desktop, Claude Code, Cursor, MCP Inspector) to the Smarter Weather MCP server
Retrieve real-time and forecasted weather data via MCP with OAuth2.1 + PKCE
Authenticate once, with tokens cached for seamless subsequent access
Integrate weather data into custom tooling and workflows

⚡ Developer Benefits

Clear bridge architecture: stdio-to-HTTP for local-to-network MCP communication
Secure authentication model with token refresh and local caching
Grounded in common MCP concepts (model-context-protocol, mcp-server, openapi)
Rich weather data topics enable flexible data retrieval and composition

⚠️ Limitations

Specific server load and rate limits not detailed in the provided excerpt
OAuth flow requires local browser consent on localhost and token caching path
Some topics may require additional configuration beyond defaults

Topics

apiclaudecursordeveloper-toolsforecastforecastingmcpmcp-servermodel-context-protocolopenapiweatherweather-apiweather-data

Captured live from the server via tools/list.

get_forecast

Complete weather overview for a location: current conditions, daily forecast (day/night periods, SPC threats, severity, CAPE, UV), active alerts, and convective outlooks in one call. Data is pre-aggregated across NBM, HRRR, GFS, RTMA, and SPC and unit-converted server-side. This is the primary weather tool; reach for lower-level tools only when you need raw observations or a specific dataset. Accepts a place name directly. Examples: {"location": "Denver"} or {"location": "Portland, OR", "days": 5} or {"lat": 41.4, "lon": -92.9}.

Parameters7

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
days	integer	optional	Number of forecast days (1-14). Default 10.
units	string	optional	Unit system for all values in the request and response: imperial (°F, mph, inches), metric (°C, km/h, mm), or si (K, m/s, mm). Defaults to imperial.
include	string	optional	Comma-separated sections: current, daily, hourly, alerts, outlooks. Default "current,daily,alerts,outlooks". Use get_hourly_forecast for hourly detail.
detail_level	string	optional	standard: compact response (~5-10KB); daily includes day_precip_probability / night_precip_probability when available (precip_probability is max of day/night). detailed: also preserves CAPE, UV, full day/night period objects, extra hourly fields (~12-20KB).

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "days": {
      "type": "integer",
      "minimum": 1,
      "maximum": 14,
      "default": 10,
      "description": "Number of forecast days (1-14). Default 10."
    },
    "units": {
      "type": "string",
      "enum": [
        "imperial",
        "metric",
        "si"
      ],
      "default": "imperial",
      "description": "Unit system for all values in the request and response: imperial (°F, mph, inches), metric (°C, km/h, mm), or si (K, m/s, mm). Defaults to imperial."
    },
    "include": {
      "type": "string",
      "default": "current,daily,alerts,outlooks",
      "description": "Comma-separated sections: current, daily, hourly, alerts, outlooks. Default \"current,daily,alerts,outlooks\". Use get_hourly_forecast for hourly detail."
    },
    "detail_level": {
      "type": "string",
      "enum": [
        "standard",
        "detailed"
      ],
      "default": "standard",
      "description": "standard: compact response (~5-10KB); daily includes day_precip_probability / night_precip_probability when available (precip_probability is max of day/night). detailed: also preserves CAPE, UV, full day/night period objects, extra hourly fields (~12-20KB)."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_hourly_forecast

Blended hourly forecast: temperature, feels-like, humidity, wind, precipitation probability/amount, conditions, and icon per hour. Snapped to the current hour so hourly[0] is "now". Timestamps are UTC ISO 8601; convert to the local timezone before presenting. Ask for the days you need up front -- one call with days: 4 beats four calls. ALWAYS check hourly_coverage before answering about a specific hour: it reports first_time and last_time (the window the rows actually span), sample_interval_hours (past the first day rows are every 2-3h, not every hour), and truncated: true when upstream returned less than you asked for. If the hour the user cares about is after last_time, say the forecast does not reach that far yet rather than answering from the nearest row you do have. For one stretch of time ask for that stretch with hours_from/hours_to: it comes back hour by hour even where the full range would be sampled. Accepts a place name or coordinates. Examples: {"location": "Portland, OR", "days": 2} or {"lat": 41.88, "lon": -87.63, "hours_from": 36, "hours_to": 48}.

Parameters8

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
days	integer	optional	Days of hourly data (1-7). Default 2. Widened when hours_to reaches further.
hours_from	integer	optional	Window start, in hours from now (0 = the current hour).
hours_to	integer	optional	Window end, in hours from now, exclusive. 36 to 48 is hours 36-47.
units	string	optional	Unit system for all values in the request and response: imperial (°F, mph, inches), metric (°C, km/h, mm), or si (K, m/s, mm). Defaults to imperial.
detail_level	string	optional	standard: compact hourly data (sampled past 24h). detailed: preserves CAPE, ceiling, UV, gust, thunderstorm probability for the first 48h.

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "days": {
      "type": "integer",
      "minimum": 1,
      "maximum": 7,
      "default": 2,
      "description": "Days of hourly data (1-7). Default 2. Widened when hours_to reaches further."
    },
    "hours_from": {
      "type": "integer",
      "minimum": 0,
      "maximum": 168,
      "description": "Window start, in hours from now (0 = the current hour)."
    },
    "hours_to": {
      "type": "integer",
      "minimum": 1,
      "maximum": 168,
      "description": "Window end, in hours from now, exclusive. 36 to 48 is hours 36-47."
    },
    "units": {
      "type": "string",
      "enum": [
        "imperial",
        "metric",
        "si"
      ],
      "default": "imperial",
      "description": "Unit system for all values in the request and response: imperial (°F, mph, inches), metric (°C, km/h, mm), or si (K, m/s, mm). Defaults to imperial."
    },
    "detail_level": {
      "type": "string",
      "enum": [
        "standard",
        "detailed"
      ],
      "default": "standard",
      "description": "standard: compact hourly data (sampled past 24h). detailed: preserves CAPE, ceiling, UV, gust, thunderstorm probability for the first 48h."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

search_locations

Resolve a place query to candidate locations with coordinates. Accepts city names ("Denver"), city+state ("Portland, OR" via query), ZIP codes ("50219"), or partial input with fuzzy=true for autosuggest-style matching ("bost" -> Boston). Returns ranked candidates with lat/lon. Most weather tools accept a `location` string directly and geocode internally -- use this tool only to disambiguate ("which Springfield?") or to present location choices to the user. Example: {"query": "Springfield"} returns all major Springfields ranked by place importance.

Parameters3

query	string	required	Place query: city, "city, state", ZIP, or partial text with fuzzy=true.
fuzzy	boolean	optional	Autosuggest mode for partial/misspelled input. Default false (exact search).
limit	integer	optional	Maximum candidates to return (1-10). Default 5.

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Place query: city, \"city, state\", ZIP, or partial text with fuzzy=true."
    },
    "fuzzy": {
      "type": "boolean",
      "default": false,
      "description": "Autosuggest mode for partial/misspelled input. Default false (exact search)."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 10,
      "default": 5,
      "description": "Maximum candidates to return (1-10). Default 5."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

reverse_geocode

Resolve coordinates to a human-readable place (city, state, county, timezone). Use when you have lat/lon but need a display name or the local timezone. Example: {"lat": 39.74, "lon": -104.99} -> Denver, Colorado, America/Denver.

Parameters2

lat	number	required	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	required	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).

Raw schema

{
  "type": "object",
  "properties": {
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    }
  },
  "required": [
    "lat",
    "lon"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_alerts

NWS watches, warnings, advisories. Point (city/ZIP/lat+lon): containing polygons. BBox or US state/DC/CONUS (codes, full names, US/national): intersecting polygons. A city miss is not a statewide all-clear — query the state or a bbox; never say regional inventory is impossible. NY/WA and "New York State"/"Washington State" are states; "New York"/"Washington" stay cities. Omit at for now; at (ISO-8601 UTC) is the snapshot then. Empty = all-clear or purged (~24h). alert_id = detail+geometry, ignores at. Ex: {"location":"WI","events":["Tornado Warning"]}.

Parameters7

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
bbox	object	optional	Bounding box {west,south,east,north}. Skips geocoding; intersecting polygons.
events	array	optional	Optional event-name filter, e.g. ["Tornado Warning"].
alert_id	string	optional	Alert identifier for detail mode. When set, location is ignored.
at	string	optional	ISO-8601 UTC past instant for the in-effect snapshot. Ignored with alert_id.

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "bbox": {
      "type": "object",
      "properties": {
        "west": {
          "$ref": "#/properties/lon"
        },
        "south": {
          "$ref": "#/properties/lat"
        },
        "east": {
          "$ref": "#/properties/lon"
        },
        "north": {
          "$ref": "#/properties/lat"
        }
      },
      "required": [
        "west",
        "south",
        "east",
        "north"
      ],
      "additionalProperties": false,
      "description": "Bounding box {west,south,east,north}. Skips geocoding; intersecting polygons."
    },
    "events": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional event-name filter, e.g. [\"Tornado Warning\"]."
    },
    "alert_id": {
      "type": "string",
      "description": "Alert identifier for detail mode. When set, location is ignored."
    },
    "at": {
      "type": "string",
      "description": "ISO-8601 UTC past instant for the in-effect snapshot. Ignored with alert_id."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_time_context

Complete temporal context for a location: local time, timezone, 14-day calendar with day names and Today/Tomorrow offsets, sunrise/sunset/solar times (from the weather pipeline's astro product), and moon phase. Use whenever you need to reason about dates, times, or daylight for a location -- including "what time is sunset?", "is it dark there now?", or "what day of the week is the 4th-day forecast?". Accepts a place name directly. Example: {"location": "Seattle"}.

Parameters3

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_period_totals

Aggregate a weather variable over one or more time periods. Returns server-computed totals, maxima, minima, or averages per period. Period start/end times should use the user's local timezone boundaries (not UTC midnight). Response includes the converted value and unit per period. Ideal for questions like "total rainfall today and tomorrow" or "peak wind speed this weekend". Accepts a place name directly. Example: {"location": "Portland, OR", "variable": "precipitation", "aggregation": "sum", "periods": [{"start": "2026-07-08T07:00:00Z", "end": "2026-07-09T07:00:00Z", "label": "Today"}]}.

Parameters8

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
variable	string	required	Standard variable name (e.g. precipitation, snowfall, temperature_2m, wind_speed_10m, cape).
aggregation	string	optional	Aggregation function. Default sum. Use sum for precipitation/snowfall, max for temperature/wind, min for low temperatures, avg for humidity/cloud cover.
periods	array	required	Time periods to aggregate over (1-14).
units	string	optional	Unit system for all values in the request and response: imperial (°F, mph, inches), metric (°C, km/h, mm), or si (K, m/s, mm). Defaults to imperial.
dataset_id	string	optional	Dataset override. Default: auto-resolved NBM for the location.

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "variable": {
      "type": "string",
      "description": "Standard variable name (e.g. precipitation, snowfall, temperature_2m, wind_speed_10m, cape)."
    },
    "aggregation": {
      "type": "string",
      "enum": [
        "sum",
        "max",
        "min",
        "avg"
      ],
      "default": "sum",
      "description": "Aggregation function. Default sum. Use sum for precipitation/snowfall, max for temperature/wind, min for low temperatures, avg for humidity/cloud cover."
    },
    "periods": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "start": {
            "type": "string",
            "description": "ISO 8601 start time"
          },
          "end": {
            "type": "string",
            "description": "ISO 8601 end time"
          },
          "label": {
            "type": "string",
            "description": "Human label, e.g. \"Today\", \"Tomorrow\""
          }
        },
        "required": [
          "start",
          "end"
        ],
        "additionalProperties": false
      },
      "minItems": 1,
      "maxItems": 14,
      "description": "Time periods to aggregate over (1-14)."
    },
    "units": {
      "type": "string",
      "enum": [
        "imperial",
        "metric",
        "si"
      ],
      "default": "imperial",
      "description": "Unit system for all values in the request and response: imperial (°F, mph, inches), metric (°C, km/h, mm), or si (K, m/s, mm). Defaults to imperial."
    },
    "dataset_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 80,
      "description": "Dataset override. Default: auto-resolved NBM for the location."
    }
  },
  "required": [
    "variable",
    "periods"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

compare_locations

Compare forecast variables across multiple locations side-by-side in one batched call. Returns a distilled per-location series matrix for direct comparison -- prefer this over N sequential forecast calls. Locations accept place names directly. Example: {"locations": [{"location": "Denver"}, {"location": "Boulder, CO"}], "variables": ["temperature_2m", "precipitation_probability"], "hours": 48}.

Parameters4

locations	array	required	Locations to compare (2-10). Each takes location OR lat/lon, optional label.
variables	array	required	Standard variable names (e.g. temperature_2m, precipitation).
hours	integer	optional	Forecast hours. Default 24.
dataset_id	string	optional	Dataset override. Default: auto-resolved NBM per location.

Raw schema

{
  "type": "object",
  "properties": {
    "locations": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "location": {
            "type": "string",
            "description": "Place name, ZIP, or \"lat,lon\" (e.g. \"Denver\", \"Boulder, CO\")."
          },
          "lat": {
            "type": "number",
            "minimum": -90,
            "maximum": 90
          },
          "lon": {
            "type": "number",
            "minimum": -180,
            "maximum": 180
          },
          "label": {
            "type": "string",
            "description": "Optional display label (e.g. \"Denver warehouse\")."
          }
        },
        "additionalProperties": false
      },
      "minItems": 2,
      "maxItems": 10,
      "description": "Locations to compare (2-10). Each takes location OR lat/lon, optional label."
    },
    "variables": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "maxItems": 10,
      "description": "Standard variable names (e.g. temperature_2m, precipitation)."
    },
    "hours": {
      "type": "integer",
      "minimum": 1,
      "maximum": 168,
      "default": 24,
      "description": "Forecast hours. Default 24."
    },
    "dataset_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 80,
      "description": "Dataset override. Default: auto-resolved NBM per location."
    }
  },
  "required": [
    "locations",
    "variables"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

find_best_window

Find the optimal time window for an activity based on weather criteria. Scans the forecast and returns daylight-aware periods matching all conditions. Criteria are expressed in the selected `units` system (default imperial: °F, mph, miles, feet). Example: {"location": "Boulder, CO", "criteria": {"min_temperature": 55, "max_wind_speed": 15, "max_precipitation_probability": 20}, "hours": 72, "activity_duration_hours": 3}.

Parameters8

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
units	string	optional	Unit system for all values in the request and response: imperial (°F, mph, inches), metric (°C, km/h, mm), or si (K, m/s, mm). Defaults to imperial.
criteria	object	required	Weather criteria defining acceptable conditions (all optional).
hours	integer	optional	Hours to search. Default 72.
activity_duration_hours	integer	optional	Minimum consecutive hours meeting criteria. Default 2.
daylight_only	boolean	optional	Only consider daylight hours (sunrise to sunset). Default true.

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "units": {
      "type": "string",
      "enum": [
        "imperial",
        "metric",
        "si"
      ],
      "default": "imperial",
      "description": "Unit system for all values in the request and response: imperial (°F, mph, inches), metric (°C, km/h, mm), or si (K, m/s, mm). Defaults to imperial."
    },
    "criteria": {
      "type": "object",
      "properties": {
        "max_precipitation_probability": {
          "type": "number",
          "minimum": 0,
          "maximum": 100,
          "description": "Maximum acceptable precipitation probability (0-100%)."
        },
        "min_temperature": {
          "type": "number",
          "description": "Minimum temperature in the selected units (°F / °C / K)."
        },
        "max_temperature": {
          "type": "number",
          "description": "Maximum temperature in the selected units (°F / °C / K)."
        },
        "max_wind_speed": {
          "type": "number",
          "description": "Maximum sustained wind in the selected units (mph / km/h / m/s)."
        },
        "max_wind_gust": {
          "type": "number",
          "description": "Maximum wind gust in the selected units (mph / km/h / m/s)."
        },
        "min_visibility": {
          "type": "number",
          "description": "Minimum visibility in the selected units (miles / km / m)."
        },
        "min_ceiling": {
          "type": "number",
          "description": "Minimum cloud ceiling in the selected units (feet / m / m)."
        }
      },
      "additionalProperties": false,
      "description": "Weather criteria defining acceptable conditions (all optional)."
    },
    "hours": {
      "type": "integer",
      "minimum": 1,
      "maximum": 168,
      "default": 72,
      "description": "Hours to search. Default 72."
    },
    "activity_duration_hours": {
      "type": "integer",
      "minimum": 1,
      "maximum": 24,
      "default": 2,
      "description": "Minimum consecutive hours meeting criteria. Default 2."
    },
    "daylight_only": {
      "type": "boolean",
      "default": true,
      "description": "Only consider daylight hours (sunrise to sunset). Default true."
    }
  },
  "required": [
    "criteria"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_outlooks

Hazard outlooks affecting a location. hazard=severe returns SPC convective outlooks (Day 1-8 categorical risk + tornado/wind/hail probabilities); hazard=fire returns SPC fire weather outlooks; hazard=rain returns WPC Excessive Rainfall Outlook polygons (days 1-3); hazard=heat returns the NWS HeatRisk index at the point (0 none .. 4 extreme, days 1-3). include_narrative=true adds the forecaster discussion for severe (SWO), fire (FWD), or rain (QPF/QPFERD; one PIL for all days). An empty result means no outlook covers the point -- not a failure. Examples: {"location": "Moore, OK", "hazard": "severe", "include_narrative": true} or {"location": "Phoenix", "hazard": "heat"}.

Parameters6

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
hazard	string	optional	Hazard family: severe = SPC convective, fire = SPC fire weather, rain = WPC excessive rainfall, heat = NWS HeatRisk index. (Winter/WSSI is a planned expansion.)
day	integer	optional	Outlook day for the narrative filter (1-8). Default 1.
include_narrative	boolean	optional	Include the forecaster narrative for the requested day (severe, fire, and rain).

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "hazard": {
      "type": "string",
      "enum": [
        "severe",
        "fire",
        "rain",
        "heat"
      ],
      "default": "severe",
      "description": "Hazard family: severe = SPC convective, fire = SPC fire weather, rain = WPC excessive rainfall, heat = NWS HeatRisk index. (Winter/WSSI is a planned expansion.)"
    },
    "day": {
      "type": "integer",
      "minimum": 1,
      "maximum": 8,
      "default": 1,
      "description": "Outlook day for the narrative filter (1-8). Default 1."
    },
    "include_narrative": {
      "type": "boolean",
      "default": false,
      "description": "Include the forecaster narrative for the requested day (severe, fire, and rain)."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_forecast_discussion

Expert forecaster text products. type=afd: Area Forecast Discussion. type=hwo: Hazardous Weather Outlook. type=now: WFO short-term NOW. type=fwf/hls/esf: local fire weather / hurricane local statement / hydrologic discussion. type=mcd: SPC Mesoscale Discussion. type=mpd: WPC Mesoscale Precipitation Discussion (flash flood). type=swo/fwd/ero: national outlook discussions. type=tcd/tcp/tcm/twd/two: NHC tropical text (type=two is the text TWO, not GIS nhc_two). type=pmd: WPC/CPC desk discussion (pass awips_id for a specific desk, e.g. PMDSPD). type=pwo: SPC public weather outlook. National types (swo/fwd/ero/tcd/tcp/tcm/twd/two/pmd/pwo) need no location; `day` selects the outlook day for swo and fwd. summary_only=true returns the pipeline LLM summary without the full body. Examples: {"location": "Des Moines", "type": "afd"} or {"type": "swo", "day": 2, "summary_only": true}.

Parameters9

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
type	string	required	Product type: afd (WFO discussion), hwo (hazard outlook), now (short-term NOW), fwf/hls/esf (local WFO), mcd (SPC mesoscale), mpd (WPC precipitation discussion), swo (SPC convective outlook), fwd (SPC fire weather), ero (WPC excessive rainfall), tcd/tcp/tcm/twd/two (NHC tropical text; two is text TWO not GIS), pmd (desk discussion), pwo (SPC public outlook).
day	integer	optional	Outlook day for type=swo or type=fwd (1-8). Ignored for the other types; WPC files ERO days 1-3 under one product.
awips_id	string	optional	Full AWIPS identifier (e.g. TCDAT1, PMDSPD). More specific than type + location. Exact source_ref match.
wfo	string	optional	WFO identifier override (e.g. BOU). Default: resolved from the location.
limit	integer	optional	Number of recent products (1-10). Default 1 (latest).
summary_only	boolean	optional	Return only the LLM summary + sections, omitting the full body text.

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "type": {
      "type": "string",
      "enum": [
        "afd",
        "hwo",
        "now",
        "fwf",
        "hls",
        "esf",
        "mcd",
        "mpd",
        "swo",
        "fwd",
        "ero",
        "tcd",
        "tcp",
        "tcm",
        "twd",
        "two",
        "pmd",
        "pwo"
      ],
      "description": "Product type: afd (WFO discussion), hwo (hazard outlook), now (short-term NOW), fwf/hls/esf (local WFO), mcd (SPC mesoscale), mpd (WPC precipitation discussion), swo (SPC convective outlook), fwd (SPC fire weather), ero (WPC excessive rainfall), tcd/tcp/tcm/twd/two (NHC tropical text; two is text TWO not GIS), pmd (desk discussion), pwo (SPC public outlook)."
    },
    "day": {
      "type": "integer",
      "minimum": 1,
      "maximum": 8,
      "default": 1,
      "description": "Outlook day for type=swo or type=fwd (1-8). Ignored for the other types; WPC files ERO days 1-3 under one product."
    },
    "awips_id": {
      "type": "string",
      "minLength": 3,
      "maxLength": 12,
      "description": "Full AWIPS identifier (e.g. TCDAT1, PMDSPD). More specific than type + location. Exact source_ref match."
    },
    "wfo": {
      "type": "string",
      "minLength": 3,
      "maxLength": 4,
      "description": "WFO identifier override (e.g. BOU). Default: resolved from the location."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 10,
      "default": 1,
      "description": "Number of recent products (1-10). Default 1 (latest)."
    },
    "summary_only": {
      "type": "boolean",
      "default": false,
      "description": "Return only the LLM summary + sections, omitting the full body text."
    }
  },
  "required": [
    "type"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_storm_reports

Recent NWS Local Storm Reports (LSRs) -- verified reports of tornadoes, hail, damaging winds, flooding near a location. Use to confirm severe weather occurrence or assess reported damage. valid_time is event occurrence (UTC); cite in local time. Example: {"location": "Wichita", "hours": 12, "type": "H"}.

Parameters5

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
hours	integer	optional	Lookback window in hours (1-24). Default 6.
type	string	optional	Report type filter: T=tornado, H=hail, W=wind, F=flood, D=damage, S=snow.

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "hours": {
      "type": "integer",
      "minimum": 1,
      "maximum": 24,
      "default": 6,
      "description": "Lookback window in hours (1-24). Default 6."
    },
    "type": {
      "type": "string",
      "description": "Report type filter: T=tornado, H=hail, W=wind, F=flood, D=damage, S=snow."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_lightning_activity

Real-time lightning near a location: GLM satellite flash count (30km/10min) and MRMS ground-truth lightning density + 30-minute probability. The summary field is ready-to-use. A zero flash count means no lightning inside that window -- report it as a quiet observation scoped to the window in `scope`, never as a data gap. Only call when storms may be active or the user asks about lightning. Example: {"location": "Tampa"}.

Parameters3

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_sounding

Nearest RAOB (radiosonde) vertical soundings to a point. Each sounding carries: profile (pressure-indexed thermodynamics: pressure_hpa, height_m, temperature_c, dewpoint_c, wind arrays), wind_profile (height-indexed winds for hodographs/shear), and derived indices (sbcape/mucape/mlcape + cin, lifted_index, k_index, total_totals, pwat_mm, freezing_level_m, lcl/lfc/el, bulk_shear_0_6km_kt). Soundings launch at 00Z/12Z so data can be hours old. Example: {"location": "Norman, OK"}.

Parameters4

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
n	integer	optional	Number of nearest soundings (1-5). Default 1.

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "n": {
      "type": "integer",
      "minimum": 1,
      "maximum": 5,
      "default": 1,
      "description": "Number of nearest soundings (1-5). Default 1."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_forecast_distribution

Probabilistic forecast guidance from NBM for one aspect of the weather: percentile ranges (p10-p90), exceedance probabilities, and ensemble spread. Use this for any question about odds, ranges, potential or confidence ("how much could we get", "worst case for the wind", "how sure is this") -- a deterministic forecast value cannot answer one. Reading the percentiles: p50 is the most likely outcome, p90 is the reasonable worst case when the risk is the high end (snow totals, wind, rainfall), and p10 is the reasonable worst case when the risk is the low end (cold, minimum visibility, ceiling). A single percentile is not the forecast -- report the likely value with the tail that matters, and label which is which. Aspects: precip (PoP, QPF + percentiles), snow (accumulation percentiles, >1/2/4in probabilities, snow level), ice (freezing rain, accretion), temperature (temp/dewpoint + stddev), wind (speed/gust percentiles), severe (hail/tornado/damaging-wind probabilities), aviation (LIFR/IFR/MVFR visibility + ceiling probabilities), confidence (ensemble stddev; low spread = settled forecast, high spread = details still in play). Examples: {"location": "Denver", "aspect": "snow", "hours": 72} or {"lat": 32.9, "lon": -97.0, "aspect": "severe"}.

Parameters5

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
aspect	string	required	Which distribution family to return (see tool description).
hours	integer	optional	Forecast hours (1-264). Default varies by aspect (48-72).

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "aspect": {
      "type": "string",
      "enum": [
        "precip",
        "snow",
        "ice",
        "temperature",
        "wind",
        "severe",
        "aviation",
        "confidence"
      ],
      "description": "Which distribution family to return (see tool description)."
    },
    "hours": {
      "type": "integer",
      "minimum": 1,
      "maximum": 264,
      "description": "Forecast hours (1-264). Default varies by aspect (48-72)."
    }
  },
  "required": [
    "aspect"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_current_conditions

Current weather right now at a location from two independent sources in one call: the RTMA gridded analysis (exact-point values, updated sub-hourly) and the nearest METAR station observation (ground truth with raw METAR, flight category). Use the analysis for point-accurate values and the station for verification. For a forecast, use get_forecast. Example: {"location": "Pella, IA"}.

Parameters3

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_observations

METAR surface observations from weather stations: temperature, wind, visibility, ceiling, flight category, raw METAR. Nearest mode (default) returns the closest N stations to a location; station mode returns history for a specific ICAO identifier. Examples: {"location": "Denver", "n": 3} or {"station": "KJFK", "hours": 6}.

Parameters6

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
n	integer	optional	Number of nearest stations (1-10). Default 1. Ignored in station mode.
station	string	optional	ICAO station identifier (e.g. KJFK). Switches to station-history mode.
hours	integer	optional	Hours of history in station mode (1-24).

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "n": {
      "type": "integer",
      "minimum": 1,
      "maximum": 10,
      "default": 1,
      "description": "Number of nearest stations (1-10). Default 1. Ignored in station mode."
    },
    "station": {
      "type": "string",
      "minLength": 3,
      "maxLength": 4,
      "description": "ICAO station identifier (e.g. KJFK). Switches to station-history mode."
    },
    "hours": {
      "type": "integer",
      "minimum": 1,
      "maximum": 24,
      "description": "Hours of history in station mode (1-24)."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

list_datasets

Discover the datasets (model grids, analyses, observations) available at a location, with per-dataset freshness (data age, latest model run). Datasets vary by domain (CONUS/Alaska/Hawaii). Use this to find dataset_id values for query_dataset and describe_dataset, or to assess whether data is current before making decisions. Example: {"location": "Anchorage"}.

Parameters4

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
include_freshness	boolean	optional	Include per-dataset data age and run times. Default true.

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "include_freshness": {
      "type": "boolean",
      "default": true,
      "description": "Include per-dataset data age and run times. Default true."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

describe_dataset

Variables available in a dataset, with standard names, units, descriptions, and the time range of available data. Use before query_dataset to discover valid variable names. Example: {"dataset_id": "nbm_conus"}.

Parameters1

dataset_id

string

required

Pipeline dataset identifier (e.g. "nbm_conus", "mrms_reflectivity_conus"). Discover valid values with list_datasets; inspect variables with describe_dataset.

Raw schema

{
  "type": "object",
  "properties": {
    "dataset_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 80,
      "description": "Pipeline dataset identifier (e.g. \"nbm_conus\", \"mrms_reflectivity_conus\"). Discover valid values with list_datasets; inspect variables with describe_dataset."
    }
  },
  "required": [
    "dataset_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

query_dataset

Raw time series from a specific dataset for specific variables at a point. Power-user access to any gridded product (NBM, HRRR, RRFS, GFS, RTMA, MRMS, air quality, ...). Time modes: hours (next N hours, default 24), time_start+time_end (explicit ISO-8601 window), or latest=true (single most-recent value). reference_time pins a specific model run, and each returned series reports the run that served it (reference_time, or reference_times when a series mixes runs) — check it before comparing two runs, since a run older than about 48 hours may no longer be available. For blended forecasts use get_forecast instead. Examples: {"location": "Denver", "dataset_id": "rrfs_surface", "variables": ["temperature_2m"], "hours": 18} or {"lat": 41.4, "lon": -92.9, "dataset_id": "rtma_conus", "variables": ["temperature_2m"], "latest": true}.

Parameters10

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
dataset_id	string	optional	Dataset to query. Default: the NBM dataset for the location domain (nbm_conus/nbm_alaska/nbm_hawaii). Discover options with list_datasets.
variables	array	required	Standard variable names (e.g. temperature_2m, precipitation). Discover with describe_dataset.
hours	integer	optional	Forecast/lookahead hours from now (1-264). Default 24 when no other time mode set.
time_start	string	optional	ISO 8601 window start (with time_end).
time_end	string	optional	ISO 8601 window end (with time_start).
latest	boolean	optional	Return only the most recent value (analysis datasets like RTMA/MRMS).
reference_time	string	optional	Pin a specific model run (ISO 8601). Default: latest run.

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "dataset_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 80,
      "description": "Dataset to query. Default: the NBM dataset for the location domain (nbm_conus/nbm_alaska/nbm_hawaii). Discover options with list_datasets."
    },
    "variables": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "maxItems": 20,
      "description": "Standard variable names (e.g. temperature_2m, precipitation). Discover with describe_dataset."
    },
    "hours": {
      "type": "integer",
      "minimum": 1,
      "maximum": 264,
      "description": "Forecast/lookahead hours from now (1-264). Default 24 when no other time mode set."
    },
    "time_start": {
      "type": "string",
      "description": "ISO 8601 window start (with time_end)."
    },
    "time_end": {
      "type": "string",
      "description": "ISO 8601 window end (with time_start)."
    },
    "latest": {
      "type": "boolean",
      "default": false,
      "description": "Return only the most recent value (analysis datasets like RTMA/MRMS)."
    },
    "reference_time": {
      "type": "string",
      "description": "Pin a specific model run (ISO 8601). Default: latest run."
    }
  },
  "required": [
    "variables"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_growing_degree_days

Growing Degree Units (GDU / GDD) for a US location (CONUS, Alaska, Hawaii), computed from daily max/min temperatures. Pass a crop id (e.g. "corn", "soybean", "wheat") to use calibrated base/upper thresholds, or crop="custom" with base_temp_c (and optional upper_temp_c / method). Without season_start you get per-day GDU across the forecast horizon; WITH season_start (YYYY-MM-DD) you get the cumulative season-to-date total (observed history + today + forecast) plus a per-day cumulative series -- the number a grower tracks against crop milestones. Answers "how many growing degree days has my corn accumulated since May 1?" and "what's the GDU forecast this week?".

Parameters11

lat	number	required	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	required	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
crop	string	required	Crop id from the catalog (e.g. "corn", "soybean", "wheat") or "custom" to supply your own thresholds via base_temp_c.
season_start	string	optional	Season/planting start as YYYY-MM-DD (local date). Presence switches the response to a cumulative season-to-date GDU total. Must be within the ~180-day observed window.
days	integer	optional	Forecast horizon in days (default 10).
day_definition	string	optional	Daily boundary: "nws" (default; NBM MaxT/MinT period extremes) or "local_calendar" (midnight-to-midnight local day).
unit	string	optional	Unit system for GDU + temps. Default imperial (°F-days).
base_temp_c	number	optional	Custom base threshold in °C. Required when crop="custom".
upper_temp_c	number	optional	Custom upper cutoff in °C (enables the modified method). Optional.
method	string	optional	GDU method for custom crops. Defaults from whether upper_temp_c is set.
include_milestones	boolean	optional	Include the crop's growth-stage GDU milestones in the response.

Raw schema

{
  "type": "object",
  "properties": {
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "crop": {
      "type": "string",
      "description": "Crop id from the catalog (e.g. \"corn\", \"soybean\", \"wheat\") or \"custom\" to supply your own thresholds via base_temp_c."
    },
    "season_start": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Season/planting start as YYYY-MM-DD (local date). Presence switches the response to a cumulative season-to-date GDU total. Must be within the ~180-day observed window."
    },
    "days": {
      "type": "integer",
      "minimum": 1,
      "maximum": 30,
      "description": "Forecast horizon in days (default 10)."
    },
    "day_definition": {
      "type": "string",
      "enum": [
        "nws",
        "local_calendar"
      ],
      "description": "Daily boundary: \"nws\" (default; NBM MaxT/MinT period extremes) or \"local_calendar\" (midnight-to-midnight local day)."
    },
    "unit": {
      "type": "string",
      "enum": [
        "imperial",
        "metric"
      ],
      "description": "Unit system for GDU + temps. Default imperial (°F-days)."
    },
    "base_temp_c": {
      "type": "number",
      "description": "Custom base threshold in °C. Required when crop=\"custom\"."
    },
    "upper_temp_c": {
      "type": "number",
      "description": "Custom upper cutoff in °C (enables the modified method). Optional."
    },
    "method": {
      "type": "string",
      "enum": [
        "simple",
        "modified"
      ],
      "description": "GDU method for custom crops. Defaults from whether upper_temp_c is set."
    },
    "include_milestones": {
      "type": "boolean",
      "description": "Include the crop's growth-stage GDU milestones in the response."
    }
  },
  "required": [
    "lat",
    "lon",
    "crop"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_climate_normals

Day-of-year climate normals (NCEI 1991-2020 30-year averages) for a US location, from the nearest station with a record. Returns normal high, normal low, and normal mean for each date in the window, plus the station and how far away it is. Use this whenever a question needs a baseline rather than a forecast: "is this warm for October?", "what is a typical high here in January?", "how does this week compare to normal?". Pair it with get_forecast to say how far above or below normal the coming days run. Covers dates by day of year, so it answers for any date, past or future -- these are long-period averages, not a forecast and not observed history for a specific year.

Parameters6

lat	number	required	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	required	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
start	string	optional	Inclusive range start as YYYY-MM-DD. Must be supplied with end.
end	string	optional	Inclusive range end as YYYY-MM-DD. Must be supplied with start.
days	integer	optional	Range length in days when start/end are omitted; the window opens today (default 14).
unit	string	optional	Unit system for the normals. Default imperial (°F).

Raw schema

{
  "type": "object",
  "properties": {
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "start": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Inclusive range start as YYYY-MM-DD. Must be supplied with end."
    },
    "end": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Inclusive range end as YYYY-MM-DD. Must be supplied with start."
    },
    "days": {
      "type": "integer",
      "minimum": 1,
      "maximum": 366,
      "description": "Range length in days when start/end are omitted; the window opens today (default 14)."
    },
    "unit": {
      "type": "string",
      "enum": [
        "imperial",
        "metric"
      ],
      "description": "Unit system for the normals. Default imperial (°F)."
    }
  },
  "required": [
    "lat",
    "lon"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_forecast_skill

How accurate our forecasts have actually been near a location, measured against observed analysis truth. Returns bias (positive = the model runs high), mean absolute error, RMSE, and a skill score against local climatology, per model, weather variable, and forecast lead time; continuous and vector entries also carry persistenceSkillScore, skill against the analysis at forecast issue time (null means not enough persist pairs, not zero skill -- do not compare it to skillScore as if they shared a denominator), and analysisDisagreementMae, the analyses' own disagreement at that lead -- a floor on how good the forecast can look, not a skill score and not an excuse (null means the sibling row is missing or below minimumSamples); for probability forecasts, the Brier score and a reliability breakdown. Use this to qualify a forecast rather than assert it -- "NBM has been running 1.8F warm at 3-day leads near you, so treat that 72 as around 70" -- and to answer "how much should I trust this forecast", "is the model biased here", or "how accurate were you last month". Evidence is reported at three scopes side by side: the exact point (strongest, slowest to accumulate), the ~50km neighborhood, and the ~300km region. Prefer the most specific scope that has samples. Metrics below minimumSamples observations are withheld and listed under insufficientHistory with their count -- say that history is still accumulating rather than treating thin numbers as evidence. Coverage is a rolling recent window over verified US variables, not all of history. Entries are per model and their samples are not matched, so never conclude that one model beats another by comparing their numbers here. Each entry states the truth field it was measured against -- one designated analysis per variable -- so never compare numbers carrying different truth values either. Each entry also states the regime it was measured under: ALL for every observation regardless of weather, or a conditioned tier such as SEA:DJF (winter), SCN1:WINDY / SCN1:WET / SCN1:QUIET (what the forecast was showing), or JC1:NW (a circulation pattern). Pass the regime parameter to ask for a conditioned track record. It falls back, so asking for SCN1:WINDY and getting back regime ALL is a successful answer, not a missing one -- always read the regime field and qualify the claim with it, because "NBM runs warm here when it shows windy" and "NBM runs warm here" are different statements. Regimes overlap by construction across families, so entries under different regimes are alternative answers to one question and must never be compared or added; within SCN1: the labels are mutually exclusive. Entries with a categorical block answer a yes/no question instead of an error magnitude -- did it rain, at the thresholdMm stated on the entry -- with pod (of the times it happened, how often we called it), far (of the times we called it, how often it did not happen), and frequencyBias (above 1 = we call it too often). Use these for "will it actually rain" questions, where a small average error means nothing if the rain lands in the wrong hour. A null rate means the sample cannot answer it -- the event has not happened, or been forecast, enough times to divide by -- and must be reported as unknown, never as zero. The counts beside it are still evidence, and for a rare event they are often the whole answer: "it has only rained twice here in the record" is a useful thing to say.

Parameters9

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
variable	string	optional	Narrow to one variable, e.g. temperature_2m, dew_point_2m, wind_speed_10m, wind_gusts_10m, wind_vector_10m, cloud_cover, precipitation, precipitation_probability, or a thresholded rain event such as precipitation_gt_0p254mm (any measurable rain) or precipitation_gt_2p54mm. Omit for everything measured at the location.
model	string	optional	Narrow to one model, e.g. nbm or rrfs.
lead_hours	integer	optional	Narrow to the lead time being asked about, in hours; the containing lead bucket is selected for you (60 gives the 48-72h bucket). Use the lead of the forecast you are qualifying: ~24 for tomorrow, ~72 for three days out. Never approximated -- a lead we have not verified returns no entries rather than a nearby bucket, so an empty result means we cannot speak to that range.
truth	string	optional	Measure against a named truth source instead of the default one for each variable, e.g. urma. Only pass this if the user asked which analysis was used or named one; the default is already the designated source, and the analyses disagree, so switching changes the numbers.
regime	string	optional	Ask for a track record measured only under particular conditions, as a comma-separated preference chain, most specific first, e.g. "SCN1:WINDY,SEA:JJA". SEA: is the meteorological season (DJF, MAM, JJA, SON); SCN1: is a forecast-conditioned scenario (WINDY, WET, QUIET — mutually exclusive within the family); JC1: is a circulation pattern. The most specific tier with enough observations answers and the unconditioned record is the last resort, so this never empties a result the way truth does -- it degrades. Read the regime field on each entry to see which tier actually answered. Pass this when the question is conditional ("is it worse in winter", "how does it do when the model shows windy"); omit it otherwise, since conditioned tiers are thinner and slower to earn numbers.
unit	string	optional	Units for the error magnitudes. Default imperial (bias/MAE/RMSE in °F, mph, in).

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "variable": {
      "type": "string",
      "description": "Narrow to one variable, e.g. temperature_2m, dew_point_2m, wind_speed_10m, wind_gusts_10m, wind_vector_10m, cloud_cover, precipitation, precipitation_probability, or a thresholded rain event such as precipitation_gt_0p254mm (any measurable rain) or precipitation_gt_2p54mm. Omit for everything measured at the location."
    },
    "model": {
      "type": "string",
      "description": "Narrow to one model, e.g. nbm or rrfs."
    },
    "lead_hours": {
      "type": "integer",
      "minimum": 1,
      "description": "Narrow to the lead time being asked about, in hours; the containing lead bucket is selected for you (60 gives the 48-72h bucket). Use the lead of the forecast you are qualifying: ~24 for tomorrow, ~72 for three days out. Never approximated -- a lead we have not verified returns no entries rather than a nearby bucket, so an empty result means we cannot speak to that range."
    },
    "truth": {
      "type": "string",
      "description": "Measure against a named truth source instead of the default one for each variable, e.g. urma. Only pass this if the user asked which analysis was used or named one; the default is already the designated source, and the analyses disagree, so switching changes the numbers."
    },
    "regime": {
      "type": "string",
      "description": "Ask for a track record measured only under particular conditions, as a comma-separated preference chain, most specific first, e.g. \"SCN1:WINDY,SEA:JJA\". SEA: is the meteorological season (DJF, MAM, JJA, SON); SCN1: is a forecast-conditioned scenario (WINDY, WET, QUIET — mutually exclusive within the family); JC1: is a circulation pattern. The most specific tier with enough observations answers and the unconditioned record is the last resort, so this never empties a result the way truth does -- it degrades. Read the regime field on each entry to see which tier actually answered. Pass this when the question is conditional (\"is it worse in winter\", \"how does it do when the model shows windy\"); omit it otherwise, since conditioned tiers are thinner and slower to earn numbers."
    },
    "unit": {
      "type": "string",
      "enum": [
        "imperial",
        "metric",
        "si"
      ],
      "description": "Units for the error magnitudes. Default imperial (bias/MAE/RMSE in °F, mph, in)."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_forecast_skill_map

Measured forecast skill as a map of res-4 hexes inside a bounding box, sliced from the public skill map. Use this when the question is spatial ("where is NBM temperature skill weak across Colorado"), not "how good is the forecast at this point" — that is get_forecast_skill. Requires model, variable, lead_hours, and bbox {west,south,east,north}. lead_hours selects the containing published bucket (20 → NBM 24); a lead we have not published returns no slices rather than a nearby one. A hex is included when its center is inside the box; edge-overlapping hexes are dropped. The box cannot wrap the dateline. Each cell is [h3, samples, skill_score]; skill_score is unitless (fraction of climatological variance explained) and already gated at n ≥ 30. withheld lists hexes still accumulating. Do not compare slices across models or truths. This is CELL# only — never treat a hex as a person.

Parameters5

bbox	object	required	Bounding box {west,south,east,north}. Hexes whose H3 center falls inside are returned.
model	string	required	Model id, e.g. nbm, gfs, hrrr, or rrfs.
variable	string	required	Verified variable, e.g. temperature_2m, dew_point_2m, precipitation, or precipitation_gt_0p254mm.
lead_hours	integer	required	Lead time in hours; the containing published bucket is selected. Never approximated.
domain	string	optional	Optional domain (conus, alaska, hawaii). Omit unless you already know it.

Raw schema

{
  "type": "object",
  "properties": {
    "bbox": {
      "type": "object",
      "properties": {
        "west": {
          "type": "number",
          "minimum": -180,
          "maximum": 180,
          "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
        },
        "south": {
          "type": "number",
          "minimum": -90,
          "maximum": 90,
          "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
        },
        "east": {
          "$ref": "#/properties/bbox/properties/west"
        },
        "north": {
          "$ref": "#/properties/bbox/properties/south"
        }
      },
      "required": [
        "west",
        "south",
        "east",
        "north"
      ],
      "additionalProperties": false,
      "description": "Bounding box {west,south,east,north}. Hexes whose H3 center falls inside are returned."
    },
    "model": {
      "type": "string",
      "description": "Model id, e.g. nbm, gfs, hrrr, or rrfs."
    },
    "variable": {
      "type": "string",
      "description": "Verified variable, e.g. temperature_2m, dew_point_2m, precipitation, or precipitation_gt_0p254mm."
    },
    "lead_hours": {
      "type": "integer",
      "minimum": 1,
      "description": "Lead time in hours; the containing published bucket is selected. Never approximated."
    },
    "domain": {
      "type": "string",
      "description": "Optional domain (conus, alaska, hawaii). Omit unless you already know it."
    }
  },
  "required": [
    "bbox",
    "model",
    "variable",
    "lead_hours"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_tropical

Active NHC (National Hurricane Center) tropical systems: forecast cones, track lines, forecast points, coastal watches/warnings, and 7-day Tropical Weather Outlook formation areas -- Atlantic + East Pacific. Each feature carries a kind (cone | track | points | watch_warning | outlook_area) plus storm name, intensity, and timing properties. include_geometry=true adds full GeoJSON geometries (large). An empty result means no active tropical activity. Example: {} or {"include_geometry": true}.

Parameters1

include_geometry

boolean

optional

Include full GeoJSON geometries (cone/track polygons). Default false.

Raw schema

{
  "type": "object",
  "properties": {
    "include_geometry": {
      "type": "boolean",
      "default": false,
      "description": "Include full GeoJSON geometries (cone/track polygons). Default false."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_population_exposure

National population-exposure headline for a risk-zone outlook product: how many people are inside risk bands at or above min_level. Powers headlines like "~57M people under major heat risk tomorrow". hazard=heat covers NWS HeatRisk days 1-3 (levels: 1 minor, 2 moderate, 3 major, 4 extreme). Pass product_id directly for other risk-zone products. Example: {"hazard": "heat", "min_level": 3}.

Parameters3

hazard	string	optional	Hazard family (expands the day-1..3 product set). Currently: heat (HeatRisk).
product_id	string	optional	Explicit risk-zone product ID (overrides hazard), e.g. heatrisk_day1_conus.
min_level	integer	optional	Minimum risk level to count (>=). Default 1 (any elevated risk).

Raw schema

{
  "type": "object",
  "properties": {
    "hazard": {
      "type": "string",
      "enum": [
        "heat"
      ],
      "description": "Hazard family (expands the day-1..3 product set). Currently: heat (HeatRisk)."
    },
    "product_id": {
      "type": "string",
      "description": "Explicit risk-zone product ID (overrides hazard), e.g. heatrisk_day1_conus."
    },
    "min_level": {
      "type": "integer",
      "minimum": 1,
      "maximum": 5,
      "default": 1,
      "description": "Minimum risk level to count (>=). Default 1 (any elevated risk)."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_climate_records

NWS daily climate data: type=reports returns CLI daily climate reports (observed high/low/precip vs normals per station); type=records returns RER record event reports (record highs/lows/rainfall actually set). Filter by wfo (3-letter office, e.g. DMX), station, date (YYYY-MM-DD), start/end range, or hours lookback. Examples: {"type": "records", "hours": 48} or {"type": "reports", "wfo": "DMX", "date": "2026-07-04"}.

Parameters8

type	string	required	reports = CLI daily climate reports; records = RER record events.
wfo	string	optional	WFO office filter (e.g. DMX, OUN).
station	string	optional	Station identifier filter (reports only).
record_type	string	optional	Record type filter (records only), e.g. HIGH, LOW, RAIN.
date	string	optional	Single date, YYYY-MM-DD.
start	string	optional	Range start date, YYYY-MM-DD.
end	string	optional	Range end date, YYYY-MM-DD.
hours	integer	optional	Lookback window in hours (1-168) when no date/range is given.

Raw schema

{
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "enum": [
        "reports",
        "records"
      ],
      "description": "reports = CLI daily climate reports; records = RER record events."
    },
    "wfo": {
      "type": "string",
      "minLength": 3,
      "maxLength": 4,
      "description": "WFO office filter (e.g. DMX, OUN)."
    },
    "station": {
      "type": "string",
      "description": "Station identifier filter (reports only)."
    },
    "record_type": {
      "type": "string",
      "description": "Record type filter (records only), e.g. HIGH, LOW, RAIN."
    },
    "date": {
      "type": "string",
      "description": "Single date, YYYY-MM-DD."
    },
    "start": {
      "type": "string",
      "description": "Range start date, YYYY-MM-DD."
    },
    "end": {
      "type": "string",
      "description": "Range end date, YYYY-MM-DD."
    },
    "hours": {
      "type": "integer",
      "minimum": 1,
      "maximum": 168,
      "description": "Lookback window in hours (1-168) when no date/range is given."
    }
  },
  "required": [
    "type"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_storm_cells

Radar-identified storm cells near a location, merging NEXRAD Level III algorithm output from the nearest radar site: storm tracks (cell position, movement, forecast positions), hail index (probability of hail/severe hail + max expected size), mesocyclone detections (rotation), and TVS (tornado vortex signatures). Use during active convection to see what the radar algorithms flag. An empty result means no detected cells -- common outside active storms. Example: {"location": "Norman, OK"}.

Parameters4

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
include	array	optional	Which detection families to include. Default: all.

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "include": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "tracks",
          "hail_index",
          "mesocyclone",
          "tvs"
        ]
      },
      "default": [
        "tracks",
        "hail_index",
        "mesocyclone",
        "tvs"
      ],
      "description": "Which detection families to include. Default: all."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_air_quality

AirNow air quality at a location (CONUS): current overall AQI plus per-pollutant detail (PM2.5, ozone, PM10 concentrations) and the AirNow AQI forecast. AQI scale: 0-50 good, 51-100 moderate, 101-150 unhealthy for sensitive groups, 151-200 unhealthy, 201-300 very unhealthy, 301+ hazardous. pollutants=["aqi"] (default) is the cheap headline call; add pollutant keys or include_forecast=true when the user digs in. Example: {"location": "Boise", "pollutants": ["aqi", "pm25"], "include_forecast": true}.

Parameters5

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
pollutants	array	optional	Which measurements to return. aqi = combined AQI index. Default: ["aqi"].
include_forecast	boolean	optional	Also return the AirNow next-day AQI forecast.

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "pollutants": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "aqi",
          "pm25",
          "ozone",
          "pm10"
        ]
      },
      "default": [
        "aqi"
      ],
      "description": "Which measurements to return. aqi = combined AQI index. Default: [\"aqi\"]."
    },
    "include_forecast": {
      "type": "boolean",
      "default": false,
      "description": "Also return the AirNow next-day AQI forecast."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_map_snapshot

Render a weather map image for visual analysis. Simple form: pass `product` (a viz-catalog product_id like "mrms_qpe_01h_pass2_conus", "goes_truecolor_conus", "spc_day1_categorical", "hrrr_precip_hybrid_derived_conus" (future radar), "hrrr_subhourly_conus" (15-min Future Radar), "mrms_radar_nowcast_conus", "rtma_conus", "nbm_daily_temps", or "nexrad_l3:{SITE}:{PRODUCT}" for single-site radar, e.g. "nexrad_l3:TLX:N0B") plus a location and zoom (5=regional, 8=metro, 10=city). Composed form: pass `scene` -- a declarative scene document layering basemap + multiple weather products + active alerts + storm features + inline GeoJSON in one image (layers draw bottom-to-top, under basemap labels). Example scene: {"scene":"1.0","view":{"center":{"lat":43.8,"lon":-91.2},"zoom":8},"layers":[{"type":"weather","product":"goes_truecolor_conus"},{"type":"weather","product":"nexrad_l3:ARX:N0B"},{"type":"alerts","filter":{"events":["Tornado Warning"]},"onError":"skip"}]}. Alert filters (all optional, AND-combined): `ids` (specific alerts), `events`, `severities`, `minSeverity` (Extreme>Severe>Moderate>Minor>Unknown). Single-site radar keys: the address is `nexrad_l3:{SITE}:{KEY}` where KEY is `N{tilt}{measurement}` and tilt 0 is the 0.5 degree sweep -- N0B reflectivity (dBZ, where and how heavy), N0G base velocity (knots toward/away from the radar), N0S storm-relative velocity (storm motion removed, so a couplet is rotation rather than translation -- prefer it for rotation questions), N0C correlation coefficient (0-1, debris and hail), N0X differential reflectivity (dB). Legacy codes (N0V, N0R, N0Q) are accepted as aliases. Not every site produces every key; when a render reports which keys a site has, retry with one of those. Optional `time` (unix seconds): closest frame. Forecast (HRRR/nowcast/NBM) honors future times; analysis (MRMS/NEXRAD/RTMA/GOES) clamps to latest past. Pass `time` for future-radar asks — do not claim that capability is missing. Product ids must be real viz-catalog entries -- shorthand like "radar" or "reflectivity" is not one. Omit `product` for the default hybrid precip still. For Alaska and Hawaii prefer a local site or `mrms_precip_hybrid_derived_alaska` over CONUS mosaics, which do not cover them. Returns the rendered image plus per-layer resolved valid times.

Parameters10

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
product	string	optional	viz-catalog product_id or nexrad_l3:{SITE}:{KEY} (simple form)
zoom	number	optional	Map zoom (simple form)
time	integer	optional	Unix seconds; closest frame (default: latest). Forecasts honor future times.
opacity	number	optional	Weather layer opacity
width	integer	optional
height	integer	optional
scene	object	optional	Full scene document (composed form). When set, product/location/zoom are ignored.

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "product": {
      "type": "string",
      "description": "viz-catalog product_id or nexrad_l3:{SITE}:{KEY} (simple form)"
    },
    "zoom": {
      "type": "number",
      "minimum": 2,
      "maximum": 14,
      "default": 7,
      "description": "Map zoom (simple form)"
    },
    "time": {
      "type": "integer",
      "description": "Unix seconds; closest frame (default: latest). Forecasts honor future times."
    },
    "opacity": {
      "type": "number",
      "minimum": 0,
      "maximum": 1,
      "description": "Weather layer opacity"
    },
    "width": {
      "type": "integer",
      "minimum": 300,
      "maximum": 2000,
      "default": 720
    },
    "height": {
      "type": "integer",
      "minimum": 200,
      "maximum": 2000,
      "default": 440
    },
    "scene": {
      "type": "object",
      "additionalProperties": {},
      "description": "Full scene document (composed form). When set, product/location/zoom are ignored."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_sounding_chart

Render the nearest RAOB (radiosonde) sounding as a Skew-T log-P + hodograph chart image for visual analysis: temperature/dewpoint traces, wind barbs, height-banded hodograph, and a derived-indices table (CAPE/CIN, lifted index, PWAT, shear, LCL). Soundings launch at 00Z/12Z so data can be hours old. Use get_sounding for the raw profile numbers. Example: {"location": "Norman, OK"}.

Parameters5

location	string	optional	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
lat	number	optional	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lon	number	optional	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
unit	string	optional	Temperature axis display unit
scale	number	optional	Raster scale factor (2 = retina; higher = larger image payload)

Raw schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Free-text place: city (\"Denver\"), city+state (\"Portland, OR\"), US ZIP (\"50219\"), or \"lat,lon\" (\"39.74,-104.99\"). Provide either this OR explicit lat+lon, not both."
    },
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon."
    },
    "lon": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian)."
    },
    "unit": {
      "type": "string",
      "enum": [
        "fahrenheit",
        "celsius"
      ],
      "default": "fahrenheit",
      "description": "Temperature axis display unit"
    },
    "scale": {
      "type": "number",
      "minimum": 1,
      "maximum": 3,
      "default": 2,
      "description": "Raster scale factor (2 = retina; higher = larger image payload)"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_platform_status

Current data-freshness status of the weather platform: overall state, per-source states (ok / degraded / outage / no_signal), open incidents with cause attribution (provider outage vs internal processing delay), and active provider advisories. Use this when a user asks whether data is current, when other tools return surprisingly stale data, or before presenting time-critical weather. If a source is degraded or in outage, tell the user their data may be stale rather than presenting it as live. No inputs. Refreshed about every 5 minutes.

Parameters1

include_ok

boolean

optional

true: list every monitored source including healthy ones. false (default): only sources that are not ok, keeping the response compact.

Raw schema

{
  "type": "object",
  "properties": {
    "include_ok": {
      "type": "boolean",
      "default": false,
      "description": "true: list every monitored source including healthy ones. false (default): only sources that are not ok, keeping the response compact."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

packages/mcp-weather/README.md6 KBView on GitHub

@smarterweather/mcp-weather

A stdio-to-Streamable-HTTP bridge for the Smarter Weather hosted MCP server. Lets local-only MCP clients (Claude Desktop, Claude Code, Cursor, MCP Inspector, etc.) talk to sw-mcp over the network and authenticate via either:

OAuth 2.1 + PKCE (recommended for end users). The bridge runs the full MCP OAuth client — discovery, dynamic client registration, browser-based consent on localhost, and token caching at ~/.mcp-auth/. You sign in once with your SmarterWeather account; tokens auto-refresh.
SMARTERWEATHER_API_KEY environment variable. Useful for headless / CI / scripted clients that don't want a browser pop-up. The bridge forwards the key as an Authorization: Bearer … header on every proxied request.

The package itself is a thin wrapper around mcp-remote — no weather logic ships here, no protocol implementation forks. All tools, schemas, rate-limiting, and metering live server-side in sw-mcp.

Install

bash

npx -y @smarterweather/mcp-weather --version

Claude Desktop

Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):

OAuth (recommended)

json

{
  "mcpServers": {
    "smarterweather": {
      "command": "npx",
      "args": ["-y", "@smarterweather/mcp-weather"]
    }
  }
}

When Claude Desktop starts the server, your default browser opens to a SmarterWeather sign-in flow. After consent, the bridge caches the access + refresh tokens locally and Claude Desktop sees the full tool catalog (get_forecast, get_alerts, get_map_snapshot, etc.).

API key

json

{
  "mcpServers": {
    "smarterweather": {
      "command": "npx",
      "args": ["-y", "@smarterweather/mcp-weather"],
      "env": {
        "SMARTERWEATHER_API_KEY": "<from create_api_key>"
      }
    }
  }
}

Claude Desktop does not interpolate env placeholders — replace <from create_api_key> with the key in this local file (do not commit it). The bridge injects Authorization: Bearer <key> on every proxied request. No browser pop-up.

Cursor

Add to ~/.cursor/mcp.json. OAuth:

json

{
  "mcpServers": {
    "smarterweather": {
      "command": "npx",
      "args": ["-y", "@smarterweather/mcp-weather"]
    }
  }
}

API key — Cursor interpolates ${env:NAME} from the process environment:

json

{
  "mcpServers": {
    "smarterweather": {
      "command": "npx",
      "args": ["-y", "@smarterweather/mcp-weather"],
      "env": {
        "SMARTERWEATHER_API_KEY": "${env:SMARTERWEATHER_API_KEY}"
      }
    }
  }
}

Note (Cursor built-in OAuth): Cursor's built-in MCP OAuth client (cursor:// redirect) is currently incompatible with Clerk; this is tracked at SmarterWeather#7184. Using @smarterweather/mcp-weather (which delegates OAuth to mcp-remote's loopback callback) is the documented workaround — it works on Cursor today.

Dev / staging override

To point the bridge at a non-production sw-mcp deployment (e.g. a dev ALB), override the URL:

json

{
  "mcpServers": {
    "smarterweather-dev": {
      "command": "npx",
      "args": ["-y", "@smarterweather/mcp-weather"],
      "env": {
        "SMARTERWEATHER_MCP_URL": "http://<dev-alb-dns>/mcp"
      }
    }
  }
}

Or pass the URL as a positional arg (precedence: positional > env > default):

jsonc

"args": ["-y", "@smarterweather/mcp-weather", "http://<dev-alb-dns>/mcp"]

Environment variables

Variable	Purpose	Default
`SMARTERWEATHER_MCP_URL`	Override the target MCP endpoint. Useful for dev / staging.	`https://mcp.smarterweather.com`
`SMARTERWEATHER_API_KEY`	Inject `Authorization: Bearer <key>` on every proxied request. Bypasses the OAuth flow.	unset (use OAuth)
`MCP_REMOTE_CONFIG_DIR`	OAuth token cache directory (passed through to `mcp-remote`).	`~/.mcp-auth/`

Power users can pass any mcp-remote flag verbatim — they're forwarded unchanged. Examples:

--debug — verbose logs at ~/.mcp-auth/{server_hash}_debug.log.
--transport http-only — force Streamable HTTP (skip SSE fallback).
--header "X-Custom:value" — inject additional headers. Note the no-space form for cross-platform arg-escaping safety.

jsonc

"args": [
  "-y", "@smarterweather/mcp-weather",
  "--debug",
  "--transport", "http-only"
]

Troubleshooting

"Connection error: fetch failed" — verify SMARTERWEATHER_MCP_URL (or the default) is reachable from your machine. curl -i $SMARTERWEATHER_MCP_URL should return an HTTP response (a 401 with a WWW-Authenticate header is the expected unauthenticated reply for sw-mcp).
OAuth window keeps re-opening — clear stale tokens with rm -rf ~/.mcp-auth/ and restart the MCP client.
API key returns 401 — double-check the key was minted with mcp scope and isn't expired. The bridge passes the key verbatim; sw-mcp is the source of truth for which scopes a key carries.
Cursor still doesn't see the server — make sure ~/.cursor/mcp.json is valid JSON, then restart Cursor. The MCP panel logs the spawned process's stderr.

How it works (one paragraph)

The bin is a ~70-line Node script: it resolves the URL (positional arg → SMARTERWEATHER_MCP_URL → default), optionally appends --header "Authorization:Bearer $SMARTERWEATHER_API_KEY", then spawn()s mcp-remote's dist/proxy.js with the assembled argv. mcp-remote handles the actual stdio↔HTTP plumbing: it reads JSON-RPC over stdio, performs the OAuth flow if needed (discovery → DCR → PKCE → loopback callback → token cache), and proxies each message to the upstream HTTP MCP endpoint. Signals (SIGINT/SIGTERM/SIGHUP) are forwarded; exit codes propagate. The wrapper does not transform or inspect MCP traffic — it's purely a config-and-spawn shim.

License

MIT

Install

Tools (32)

get_forecastget_hourly_forecastsearch_locationsreverse_geocodeget_alertsget_time_contextget_period_totalscompare_locations

Configuration

Environment variables

SMARTERWEATHER_API_KEYsecret

Smarter Weather API key (sw_live_* or sw_test_*) with the 'mcp' scope. When set, the bridge skips the OAuth flow and forwards the key as 'Authorization: Bearer <key>' on every proxied request. When unset, the bridge runs the full MCP OAuth 2.1 + PKCE client and caches tokens at ~/.mcp-auth/. Mint keys at https://smarterweather.com/developers/api-keys.

SMARTERWEATHER_MCP_URLdefault https://mcp.smarterweather.com

Override the target MCP endpoint. Useful for development or staging against a non-production sw-mcp deployment. Precedence: positional argument > SMARTERWEATHER_MCP_URL > package default (https://mcp.smarterweather.com).

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "weather": {
      "command": "npx",
      "args": [
        "-y",
        "@smarterweather/mcp-weather@0.0.1"
      ],
      "env": {
        "SMARTERWEATHER_API_KEY": "<YOUR_SMARTERWEATHER_API_KEY>",
        "SMARTERWEATHER_MCP_URL": "https://mcp.smarterweather.com"
      }
    }
  }
}