noaa-climate-mcp-server
Server Details
Search NOAA climate stations and datasets, fetch historical weather observations.
- Status
- Healthy
- Uptime
- 99.9% over 79 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- cyanheads/noaa-climate-mcp-server
- GitHub Stars
- 4
- Server Listing
- NOAA Climate MCP Server
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 10 tools
Each tool has a clearly distinct role: CDO discovery (datasets, data types, categories, locations, stations), CDO data retrieval, single-station metadata, and separate NCEI storm/disaster corpora. The find/list/get distinctions are well explained, and overlap between location categories and location search is minimal.
All tools use the same noaa_climate_ prefix and a consistent snake_case verb_noun pattern: fetch_data, find_locations, find_stations, get_station, list_datasets, search_storm_events, etc. The long get_billion_dollar_disasters name is verbose but still follows the convention.
Ten tools is well scoped for a NOAA climate data server. The set separates discovery, station metadata, CDO observation retrieval, storm events, and disaster statistics without excessive fragmentation.
The surface covers the main read-only workflows: discover datasets/types/categories/locations/stations, fetch observations, inspect station metadata, search storm events, and query billion-dollar disasters. Minor gaps exist, such as no direct get-dataset or get-location-detail endpoint, but list/search tools provide workable coverage.
Available Tools
10 toolsnoaa_climate_fetch_dataFetch NOAA Climate Observation DataARead-onlyInspect
Fetch historical observation records from a NOAA CDO dataset for a given date range. Requires datasetId, startDate, and endDate; optionally filter stations, locations, and datatypes. The encoded query is limited to 4000 characters; reduce filters and make separate calls if exceeded. Sub-daily, daily, and radar datasets allow 1 year; GSOM/GSOY/NORMAL_MLY/NORMAL_ANN allow 10 years, through the end of the corresponding calendar month. For NORMAL_* use the API proxy year 2010. Request units=metric or units=standard: omitted units retain datatype-specific raw scales. Examples: GHCND TMAX/TMIN tenths °C, PRCP tenths mm, SNOW/SNWD whole mm; GSOM/GSOY temperature/precipitation °C/mm; NORMAL_* temperature normals tenths °F and precipitation normals hundredths inches; PRECIP_HLY/HPCP and PRECIP_15/QPCP hundredths inches. These examples are not universal conversion rules. Missing precipitation rows omit value and carry missing=true; GHCND flags expose quality-check failures without dropping values.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of records to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false. | |
| units | No | Request metric or standard conversion. Omission preserves datatype-specific raw values: GHCND TMAX/TMIN tenths °C, PRCP tenths mm, SNOW/SNWD whole mm; GSOM/GSOY temperature/precipitation °C/mm; NORMAL_* temperature normals tenths °F and precipitation normals hundredths inches; HPCP/QPCP hundredths inches. Examples are not complete unit metadata. Optional. | |
| offset | No | Zero-based index of the first record to return for pagination. Defaults to 0. | |
| endDate | Yes | End date for observations (YYYY-MM-DD). Must be within 1 year of startDate for sub-daily/daily/radar datasets (GHCND, PRECIP_15, PRECIP_HLY, NORMAL_DLY, NORMAL_HLY, NEXRAD2, NEXRAD3) or within 10 years for monthly/annual datasets (GSOM, GSOY, NORMAL_MLY, NORMAL_ANN) — measured to the end of the calendar month that many years after startDate, so a full calendar year (2024-01-01 to 2024-12-31) always fits. For any NORMAL_* dataset use 2010-12-31. | |
| datasetId | Yes | Dataset ID to query (e.g., GHCND for daily data, GSOM for monthly, GSOY for annual, NORMAL_DLY/MLY/ANN/HLY for 1981–2010 climate normals, NEXRAD2/NEXRAD3 for weather radar). Determines date range limit: GHCND/PRECIP_*/NORMAL_DLY/NORMAL_HLY/NEXRAD2/NEXRAD3 allow 1-year max per request; GSOM/GSOY/NORMAL_MLY/NORMAL_ANN allow 10-year max. | |
| sortField | No | Sort results by this field. Optional. | |
| sortOrder | No | Sort direction. Optional; defaults to asc. | |
| startDate | Yes | Start date for observations (YYYY-MM-DD). For NORMAL_* datasets use 2010-01-01 regardless of the years being analyzed — 2010 is the API proxy year for all normals. | |
| stationId | No | One or more station IDs to filter by (e.g., ["GHCND:USW00024233"]). Obtain from noaa_climate_find_stations. Multiple IDs return comparative readings across stations. Optional. | |
| datatypeId | No | One or more data type IDs to include (e.g., ["TMAX", "TMIN", "PRCP"]). Without this, all data types for the dataset are returned. Use noaa_climate_list_data_types to discover valid IDs. Optional. | |
| locationId | No | One or more location IDs to filter by (e.g., ["FIPS:37", "ZIP:98101"]). Broader than stationId — returns data from all stations within the location. Optional. | |
| includemetadata | No | Include pagination metadata in the response. Defaults to true. |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Composed guidance for station ID normalization, page-limit adjustments, raw units, missing precipitation, GHCND quality-check failures, and empty or exhausted pages. Omitted when no guidance applies. |
| results | No | Flat array of observation records sorted by date by default. |
| metadata | No | Pagination metadata. Present when includemetadata=true. |
| exhausted | No | True when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise. |
| totalCount | No | Total number of matching observation records before the page limit. |
| effectiveQuery | No | Summary of the effective query: dataset, date range, units, and any station/location/datatype filters applied. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint and openWorldHint, so the description carries the burden of behavior, and it delivers real signal: query-length limits, per-dataset date-span caps, and response semantics such as 'Missing precipitation rows omit value and carry missing=true' and 'GHCND flags expose quality-check failures without dropping values'. Some of the date-range and units text duplicates the schema, but the missing-value and flag behavior is genuinely additive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loads purpose and required parameters, then layers constraints and unit caveats in decreasing priority; the 'These examples are not universal conversion rules' caveat is well placed. It is dense but mostly earns its length, with only minor duplication of the schema's units and endDate text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return shapes need not be spelled out, and annotations cover the read-only safety profile. The description covers the expensive failure modes (query-length overflow, date-span violations, unit ambiguity, missing values), though it says nothing about pagination expectations or rate limiting for what is an open-world API call.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3; every parameter is already documented in the schema with enums, patterns, defaults and examples. The description's units explanation and NORMAL_* date hint restate what the schema already says, adding little interpretation beyond it.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Fetch historical observation records from a NOAA CDO dataset for a given date range', immediately telling an agent this returns observation rows rather than discovery metadata. It does not explicitly distinguish itself from the sibling discovery tools (find_stations, list_datasets, list_data_types), though the distinction is largely self-evident from 'observation records'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives concrete operational guidance: the 4000-character encoded query cap with the instruction to 'reduce filters and make separate calls if exceeded', and the per-dataset date-span rules including the NORMAL_* proxy year 2010. It does not say when to prefer this over sibling tools or that station/datatype IDs should be resolved first — that guidance lives only in the parameter schema descriptions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
noaa_climate_find_locationsFind NOAA Climate LocationsARead-onlyInspect
Search for geographic locations by category (CITY, ST, CNTY, CNTRY, ZIP, CLIM_REG, etc.). Returns location IDs used in station search and data queries. Without locationCategoryId, returns all location types; noaa_climate_list_location_categories lists the valid values. Use locationCategoryId=ST to list US states (51 entries — small enough to retrieve completely). To find a location by name, pass nameContains alongside locationCategoryId — the CDO API has no name parameter, so this server enumerates the category and matches the substring itself. It works for any category under the size limit stated on nameContains, which is every category except ZIP; a datasetId or datacategoryId filter can bring a category back under that limit. For a category still too large, sort alphabetically with sortField=name and page through results. Location IDs: states as FIPS:37 (NC), cities as CITY:US530018 (Seattle), zip codes as ZIP:98101, countries as FIPS:US. Obtain location IDs here, then pass them to noaa_climate_find_stations or noaa_climate_fetch_data.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false. | |
| offset | No | Zero-based index of the first result to return for pagination. Defaults to 0. | |
| endDate | No | Filter to locations with data on or before this ISO date (YYYY-MM-DD). Optional. | |
| datasetId | No | Filter to locations covered by this dataset (e.g., "GHCND"). Optional. | |
| sortField | No | Sort results by this field. Use name with sortOrder=asc to browse alphabetically when searching for a specific city or location name. Optional. | |
| sortOrder | No | Sort direction. Optional; defaults to asc. | |
| startDate | No | Filter to locations with data on or after this ISO date (YYYY-MM-DD). Optional. | |
| nameContains | No | Case-insensitive substring match on the location name. The CDO API has no name parameter, so this server applies the match itself, across the whole category rather than one page — which bounds it to a category holding at most 4000 locations. Requires locationCategoryId; adding datasetId or datacategoryId narrows a category that is otherwise too large. Example: locationCategoryId="CITY" with nameContains="seattle". Optional. | |
| datacategoryId | No | Filter to locations with this data category (e.g., "TEMP"). Optional. | |
| locationCategoryId | No | Category filter. Use ST for states (51 entries), CNTY for counties, CITY for cities (large set — thousands of entries), CNTRY for countries, ZIP for zip codes, US_TERR for US territories, CLIM_REG for NOAA climate regions, CLIM_DIV for climate divisions, HYD_ACC/HYD_CAT/HYD_REG/HYD_SUB for hydrological categories. Call noaa_climate_list_location_categories when you do not know which category to use — it returns the authoritative set. Optional — omit to return all location types. |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies. |
| results | No | Matching locations. |
| metadata | No | Pagination metadata. Present when the API returns it. |
| exhausted | No | True when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise. |
| totalCount | No | Total number of matching locations before the page limit. |
| appliedNameFilter | No | The nameContains value this response was filtered by. Present only when nameContains was supplied; every count below then describes the filtered set, not the whole category. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well beyond readOnlyHint/openWorldHint by disclosing a non-obvious implementation quirk: the CDO API has no name parameter, so the server enumerates the entire category and substring-matches locally, bounding nameContains to categories of at most 4000 locations. It also flags ZIP as the one category that cannot be name-searched and offers a sort+paginate fallback, which materially changes how an agent should plan calls.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Purpose and the location-ID formats are front-loaded, and most sentences carry operational guidance. There is mild redundancy — the 4000-entry ceiling on nameContains is stated once in the description and again as 'under the size limit stated on nameContains', and the ZIP exception is explained twice.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 10-parameter, zero-required search tool this covers the full agent workflow: category choice, name search workaround with its size limit, pagination fallback, concrete ID formats (FIPS:37, CITY:US530018, ZIP:98101, FIPS:US), and the downstream tools. Return-value detail is unnecessary because an output schema exists.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3; the description earns an extra point by adding cross-parameter constraints the schema documents only in isolation (nameContains requires locationCategoryId and can be rescued by datasetId/datacategoryId, sortField=name is the paging strategy for oversized categories). It adds little on limit/offset/dates, but that is acceptable given the schema already covers them.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Opens with a specific verb+resource ('Search for geographic locations by category') and immediately states the return value (location IDs used downstream). It explicitly distinguishes itself from noaa_climate_list_location_categories (value enumeration) and from noaa_climate_find_stations / noaa_climate_fetch_data (consumers of the IDs).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives concrete when-to-use routing: omit locationCategoryId for all types, use locationCategoryId=ST for the small states set, use nameContains plus a category for name lookup, and add datasetId/datacategoryId to shrink oversized categories. It also names the explicit alternative for enumerating categories and states the downstream hand-off to find_stations and fetch_data.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
noaa_climate_find_stationsFind NOAA Climate StationsARead-onlyInspect
Search for weather observation stations by location, bounding box, dataset, and data type. Returns station IDs, names, coordinates, elevation, and data coverage dates. Filter by locationId (e.g., "FIPS:37" for all NC stations), extent (lat/lon bounding box), datasetId, datatypeId, and date range. Station IDs returned here are used as stationId in noaa_climate_fetch_data. A station must have data for the dataset and date range you want — filter by datasetId and startDate/endDate to ensure compatibility. Common station ID formats: GHCND:USW00024233, COOP:010008.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false. | |
| extent | No | Bounding box as "minLat,minLon,maxLat,maxLon": four finite signed decimal or scientific numbers with optional surrounding whitespace, latitude ±90 and longitude ±180. Equal coordinates are accepted; reversed axes return no matches, without wrapping. Example: "47.5,-122.4,47.7,-122.1". Optional. | |
| offset | No | Zero-based index of the first result to return for pagination. Defaults to 0. | |
| endDate | No | Filter to stations with data on or before this ISO date (YYYY-MM-DD). Optional. | |
| datasetId | No | Filter to stations that have data in this dataset (e.g., "GHCND" for daily observations). Optional. | |
| sortField | No | Sort results by this field. Optional. | |
| sortOrder | No | Sort direction. Optional; defaults to asc. | |
| startDate | No | Filter to stations with data on or after this ISO date (YYYY-MM-DD). Optional. | |
| datatypeId | No | Filter to stations that record these data types (e.g., ["TMAX", "TMIN", "PRCP"]). Optional. | |
| locationId | No | Filter to stations within this location ID (e.g., "FIPS:37" for NC, "CITY:US530018" for Seattle). Obtain from noaa_climate_find_locations. Optional. | |
| datacategoryId | No | Filter to stations with data in this category (e.g., "TEMP"). Optional. |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies. |
| results | No | Matching stations. |
| metadata | No | Pagination metadata. Present when the API returns it. |
| exhausted | No | True when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise. |
| totalCount | No | Total number of matching stations before the page limit. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the compatibility prerequisite (station must have data for the dataset and range) and the ID-handoff contract with noaa_climate_fetch_data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with purpose then filters then ID format guidance; every sentence carries information. Slightly dense with examples but none are wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description needn't document return structure, yet it still summarizes returned fields. Combined with 100% schema coverage and the cross-tool handoff note, an agent has everything needed to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so a 3 is the baseline. The description goes beyond the schema by giving concrete ID formats ("FIPS:37", "GHCND:USW00024233", "COOP:010008"), which is not repeated in every parameter doc, aiding correct invocation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Search) and resource (weather observation stations) plus the filter facets, and enumerates the returned fields. It also distinguishes itself from noaa_climate_fetch_data by explaining that station IDs returned here are consumed there.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly tells the agent to filter by datasetId and startDate/endDate so returned stations actually have the desired data, and points to noaa_climate_find_locations for locationId. It does not contrast with noaa_climate_get_station, so a direct alternative comparison is missing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
noaa_climate_get_billion_dollar_disastersGet NOAA Billion-Dollar DisastersARead-onlyInspect
Query NOAA/NCEI’s retired Billion-Dollar Weather and Climate Disasters archive (1980–2024), with CPI-adjusted and unadjusted costs and deaths. No years after 2024 are added; CPI adjustments are preserved from the archive, not rebased to current prices. Every cost is in WHOLE US DOLLARS, converted from each export’s declared unit (declaredCostUnit): millions per event, billions per national year, millions per state year. Default calls return individual disasters; summary=true returns per-year counts and costs by class plus an "All Disasters" total. Filter with startYear/endYear (overlapping disasters included), disasterType (exact NCEI class, e.g. "Tropical Cyclone"), minCostInUsd, and state (two-letter postal code). coveredYears reports the span actually present in the export. Under a state scope, per-event rows carry the NATIONAL cost of disasters that reached that state, never a state share, so summing states double-counts; per-year rows carry a binned range instead of a point estimate. Separate from CDO and noaa_climate_search_storm_events; no token required.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of disasters or years to return (1–100). Defaults to 50. Larger positive integers are clamped to 100 with a notice unless NOAA_CLAMP_LIMITS=false. | |
| state | No | Two-letter US postal code (e.g. "CA", "TX", "PR") scoping the query to NCEI’s per-state export instead of the national one. Per-event rows then carry the national cost of each disaster that reached the state, not a state share; per-year rows carry a binned cost range instead of a point estimate. Optional. | |
| offset | No | Zero-based index of the first matching record to return. Defaults to 0. | |
| endYear | No | Latest year to include (1980 or later). The retired archive ends in 2024; years past coveredYears.last return no records rather than an error. Optional. | |
| summary | No | Return per-year counts and costs by disaster class instead of individual disasters. Defaults to false. | |
| startYear | No | Earliest year to include (1980 or later). A disaster whose span reaches into the range is included even when it began earlier. Optional — omit for the whole record. | |
| disasterType | No | Restrict to one NCEI disaster class, written exactly as NCEI writes it. In summary mode this also drops the "All Disasters" total from each year, leaving only the named class. Optional. | |
| minCostInUsd | No | Floor on CPI-adjusted cost in whole US dollars — 1e9 is one billion. In summary mode this is compared against the year’s "All Disasters" total, or against the named disasterType when one is given; where only a binned range exists, the top of the bin has to clear the floor. Optional. |
Output Schema
| Name | Required | Description |
|---|---|---|
| cap | No | The limit that was applied. Omitted otherwise. |
| mode | No | Which shape this response carries: "events" populates disasters, "summary" populates summaries. |
| error | No | Present when the call failed. Absent on success. |
| scope | No | "US" for the national record, or the two-letter state code that was requested. |
| shown | No | Records returned on this page. Omitted otherwise. |
| notice | No | Archive retirement and preserved CPI-adjustment disclosure, composed with any clamp, empty-page, exhaustion, or truncation guidance. |
| costBasis | No | Present when a state scope is queried in events mode: every cost below is the NATIONAL cost of a disaster that reached the state, not that state’s share of it, so adding states together double-counts. Omitted for the national scope and in summary mode. |
| disasters | No | Individual disasters for the requested page. Present when mode is "events". |
| exhausted | No | True when offset is past the end of a non-empty match set — the page is empty but matches exist. Omitted otherwise. |
| summaries | No | Per-year tallies for the requested page. Present when mode is "summary". |
| truncated | No | True when more matches exist beyond this page. Omitted otherwise. |
| sourceFile | No | The exact NCEI export this response was read from, e.g. "events-US.csv". |
| totalCount | No | Records matching every filter across the whole export, before offset and limit. |
| coveredYears | No | The year span the export actually holds, read from its rows. |
| declaredCostUnit | No | The cost unit this export declares in its own preamble, e.g. "millions of dollars". Every cost below is already in whole US dollars; this names the unit it was converted from. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds substantial behavioral detail beyond the readOnlyHint/openWorldHint annotations: the archive is retired and ends in 2024, CPI adjustments are preserved rather than rebased, costs are converted to whole US dollars from declared units, and state-scoped rows carry national costs rather than state shares. These caveats are exactly the kind of operational context an agent needs before invoking the tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the dataset identity, time span, and unit caveats, and its sentences are generally substantive. It is dense for a single paragraph and repeats some schema-level filter details, but the complexity of the archive and state-scope caveats justify most of its length.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given eight parameters, full schema description coverage, an output schema, and read-only/open-world annotations, the description is complete enough for correct invocation. It covers dataset limits, default versus summary behavior, unit conversion, state-scope pitfalls, and sibling-tool separation without needing to explain return values.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3, but the description adds meaningful cross-parameter semantics: declared cost units, the fact that summing state results double-counts, how minCostInUsd behaves in summary mode, and coveredYears reporting. It does not need to re-document every parameter because the schema already does so thoroughly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description specifies a concrete verb and resource: querying NOAA/NCEI’s retired Billion-Dollar Weather and Climate Disasters archive. It clearly scopes the dataset to 1980–2024 and distinguishes the tool from CDO and noaa_climate_search_storm_events, so an agent can identify its role without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear usage context, including default per-disaster results versus summary=true for per-year counts, and names sibling tools it is separate from. However, it does not explicitly state the conditions under which an agent should choose noaa_climate_search_storm_events or CDO instead, so the alternative routing is implied rather than fully prescribed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
noaa_climate_get_stationGet NOAA Climate StationARead-onlyInspect
Fetch full metadata for a single weather station by its ID (e.g., "GHCND:USW00024233", "COOP:010008"). Returns name, coordinates, elevation, and the full date range for which data is available. Use when you have a station ID from noaa_climate_find_stations and want its complete details, or to verify a station before querying data.
| Name | Required | Description | Default |
|---|---|---|---|
| stationId | Yes | Station ID to fetch (e.g., "GHCND:USW00024233", "COOP:010008"). Obtain from noaa_climate_find_stations. Trims surrounding whitespace, uppercases IDs, and accepts bare 11-character GHCN aliases (USW00024233 → GHCND:USW00024233). Other namespaced IDs remain accepted. |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | No | Station ID. |
| name | No | Station name. |
| error | No | Present when the call failed. Absent on success. |
| notice | No | Discloses station ID normalization when an alias was supplied. |
| maxdate | No | Latest date data is available at this station (YYYY-MM-DD). Omitted when not provided. |
| mindate | No | Earliest date data is available at this station (YYYY-MM-DD). Omitted when not provided. |
| latitude | No | Station latitude in decimal degrees. Omitted when not provided by the API. |
| elevation | No | Station elevation. Unit depends on elevationUnit. Omitted when not provided. |
| longitude | No | Station longitude in decimal degrees. Omitted when not provided by the API. |
| datacoverage | No | Fractional data coverage (0–1). Omitted when not provided by the API. |
| elevationUnit | No | Unit for elevation (e.g., "Meters"). Omitted when not provided. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add context. It does so by listing what is returned (name, coordinates, elevation, full date range), though it says nothing about behavior on an unknown station ID. With an output schema present, the return-value summary is a bonus rather than a requirement.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three tight sentences: purpose first, return contents second, usage routing last. Every sentence carries information and nothing is repeated.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read-only lookup with full schema coverage and an output schema, this is nearly complete; the only missing piece is error behavior for an invalid or unknown ID. No pagination, auth, or rate-limit concerns apply here.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents the single stationId parameter, including normalization rules and alias handling; the baseline is 3. The description's example IDs largely restate what the schema provides, adding no new syntax or format meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource ('Fetch full metadata for a single weather station by its ID'), supplies two concrete ID examples, and implicitly contrasts itself with noaa_climate_find_stations, which searches rather than retrieves. An agent can distinguish it from siblings without inspecting the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It states the two clear situations to use it: when you already have a station ID from noaa_climate_find_stations, and when you need to verify a station before querying data (pointing away from noaa_climate_fetch_data). No explicit exclusions or failure guidance are given, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
noaa_climate_list_data_categoriesList NOAA Climate Data CategoriesARead-onlyInspect
List data categories that group related data types — Temperature, Precipitation, Wind, Pressure, Sunshine, Sky cover, Weather Type, and more. Use to discover what types of measurements are available before calling noaa_climate_list_data_types. Optionally filter by dataset, location, station, or date range. There are 42 categories in total.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false. | |
| offset | No | Zero-based index of the first result to return for pagination. Defaults to 0. | |
| endDate | No | Filter to categories with data on or before this ISO date (YYYY-MM-DD). Optional. | |
| datasetId | No | Filter to categories available in this dataset (e.g., "GHCND", "GSOM"). Optional. | |
| sortField | No | Sort results by this field. Optional. | |
| sortOrder | No | Sort direction. Optional; defaults to asc. | |
| startDate | No | Filter to categories with data on or after this ISO date (YYYY-MM-DD). Optional. | |
| stationId | No | Filter to categories available at this station ID. Optional. Trims surrounding whitespace, uppercases IDs, and accepts bare 11-character GHCN aliases (USW00024233 → GHCND:USW00024233). Other namespaced IDs remain accepted. | |
| locationId | No | Filter to categories available at this location ID. Optional. |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Station ID normalization, page-limit adjustment, and empty or exhausted-page guidance. Omitted when no guidance applies. |
| results | No | Matching data categories. |
| metadata | No | Pagination metadata. Present when the API returns it. |
| exhausted | No | True when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise. |
| totalCount | No | Total number of matching data categories before the page limit. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description's burden is lighter. It adds the useful fact that there are 42 categories in total — which, against the schema's default limit of 25, signals that pagination will be needed — but says nothing about whether the four filters combine as AND, what happens when a filter matches nothing, or the response shape. Adequate but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with the resource and examples, then the workflow routing, then the filter and cardinality note. Every sentence carries distinct information, and the 42-category count earns its place by contextualizing the default page size.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, return values need no explanation, and all nine parameters are optional with full schema documentation. The description covers purpose, sequencing, filtering, and result volume. The only material gap is filter-combination behavior and a pagination cue, both minor for a read-only enumeration tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so every parameter (limit clamping, offset, date patterns, station ID normalization, sort enums) is already fully documented in structured fields. The description's line "Optionally filter by dataset, location, station, or date range" merely restates a subset of those parameters and adds no format, interaction, or combination semantics. Baseline 3 is correct when the schema does all the work.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb and resource ("List data categories") and immediately enumerates concrete examples (Temperature, Precipitation, Wind, Pressure...), so the agent knows exactly what comes back. It also distinguishes itself from the nearest sibling by naming noaa_climate_list_data_types as the downstream tool, which no other sibling does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives explicit workflow positioning: "Use to discover what types of measurements are available before calling noaa_climate_list_data_types." That is a clear when-to-use rule tied to a named alternative. It stops short of stating when NOT to use it (e.g., versus noaa_climate_list_location_categories or noaa_climate_list_datasets), which would be needed for a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
noaa_climate_list_datasetsList NOAA Climate DatasetsARead-onlyInspect
List available NOAA CDO datasets with their IDs, names, and temporal coverage. Returns all ~11 datasets by default (no required parameters). Optionally filter to datasets that contain a specific data type, cover a location or station, or overlap a date range. Common datasets: GHCND (daily observations, 1763–present), GSOM (monthly summaries), GSOY (annual summaries), NORMAL_DLY/MLY/ANN/HLY (1981–2010 climate normals). Use this first to discover available datasets before calling noaa_climate_fetch_data.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false. | |
| offset | No | Zero-based index of the first result to return for pagination. Defaults to 0. | |
| endDate | No | Inclusive upper coverage bound: dataset mindate must be on or before this date. Applied locally before pagination. Optional. | |
| sortField | No | Sort results by this field. Optional. | |
| sortOrder | No | Sort direction. Optional; defaults to asc. | |
| startDate | No | Inclusive lower coverage bound: dataset maxdate must be on or after this date. Applied locally to the complete matching catalog before pagination. Optional. | |
| stationId | No | Filter to datasets covering this station ID (e.g., "GHCND:USW00024233"). Optional. Trims surrounding whitespace, uppercases IDs, and accepts bare 11-character GHCN aliases (USW00024233 → GHCND:USW00024233). Other namespaced IDs remain accepted. | |
| datatypeId | No | Filter to datasets containing these data type IDs (e.g., ["TMAX", "PRCP"]). Optional. | |
| locationId | No | Filter to datasets covering this location ID (e.g., "FIPS:37" for NC). Optional. |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Station ID normalization, page-limit adjustment, and empty or exhausted-page guidance. Omitted when no guidance applies. |
| results | No | Matching datasets. |
| metadata | No | Pagination metadata. Synthesized for date-filtered views; otherwise present when the API returns it. |
| exhausted | No | True when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise. |
| totalCount | No | Total number of matching datasets before the page limit. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: the full catalog is ~11 datasets returned by default with no required parameters, filters are applied locally before pagination, and results can be narrowed by datatype/location/station/date overlap. It doesn't mention rate limits or whether filtering is server-side vs client-side beyond the local-application note.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core action and the default behavior, then the routing advice, then optional detail. The one questionable sentence is the dataset catalogue enumeration, which is useful orientation but the longest block in the description; everything else earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need no explanation, and the description covers defaults, filter semantics, and the intended call sequence. For a 9-parameter, zero-required discovery tool this is nearly complete; only explicit guidance about the other list/get siblings is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3, but the description adds conceptual meaning the schema lacks: it explains what each filter family actually selects (datasets that contain a data type, cover a location or station, or overlap a date range), including the overlap semantics of startDate/endDate. That is real semantic lift above the field-level descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource (list NOAA CDO datasets) plus the returned fields (IDs, names, temporal coverage), and immediately distinguishes itself from the sibling noaa_climate_fetch_data by being the discovery step. Naming concrete datasets (GHCND, GSOM, GSOY, NORMAL_*) makes the scope concrete rather than generic.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says 'Use this first to discover available datasets before calling noaa_climate_fetch_data', which gives a clear sequencing rule against the most relevant sibling. It does not address when to prefer its other siblings (list_data_types, list_data_categories, find_stations), and gives no when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
noaa_climate_list_data_typesList NOAA Climate Data TypesARead-onlyInspect
List available data types (measurement labels like TMAX, TMIN, PRCP, SNOW) for a given dataset or category. Pass a datasetId to see what is measured in that dataset, or a datacategoryId (e.g., "TEMP") to see all temperature-related types. Hundreds of types exist across all datasets. Use this before calling noaa_climate_fetch_data when the data type IDs are unknown. Common GHCND types: TMAX (max temperature), TMIN (min temperature), PRCP (precipitation), SNOW (snowfall), SNWD (snow depth), AWND (average wind speed).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false. | |
| offset | No | Zero-based index of the first result to return for pagination. Defaults to 0. | |
| endDate | No | Filter to data types with data on or before this ISO date (YYYY-MM-DD). Optional. | |
| datasetId | No | Filter to data types available in this dataset (e.g., "GHCND", "GSOM"). Optional. | |
| sortField | No | Sort results by this field. Optional. | |
| sortOrder | No | Sort direction. Optional; defaults to asc. | |
| startDate | No | Filter to data types with data on or after this ISO date (YYYY-MM-DD). Optional. | |
| stationId | No | Filter to data types available at this station ID. Optional. Trims surrounding whitespace, uppercases IDs, and accepts bare 11-character GHCN aliases (USW00024233 → GHCND:USW00024233). Other namespaced IDs remain accepted. | |
| locationId | No | Filter to data types available at this location ID. Optional. | |
| datacategoryId | No | Filter to data types in this category (e.g., "TEMP" for temperature types, "PRCP" for precipitation). Optional. |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Station ID normalization, page-limit adjustment, and empty or exhausted-page guidance. Omitted when no guidance applies. |
| results | No | Matching data types. |
| metadata | No | Pagination metadata. Present when the API returns it. |
| exhausted | No | True when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise. |
| totalCount | No | Total number of matching data types before the page limit. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description is consistent with readOnlyHint=true and openWorldHint=false, and adds useful scale context ("hundreds of types exist across all datasets") and sample ID formats, which hints pagination matters. It does not, however, mention that calling with no filters returns the full set or how results are truncated, leaving pagination behavior to the schema and output schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with purpose and the key filtering choice, then the sibling routing hint, then examples. The trailing list of common GHCND types is longer than strictly necessary, but each entry pairs an ID with a plain-language label, so it earns most of its space.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return shape needn't be restated; the description covers what is missing from structured fields — when to call it, how to choose a filter, and why IDs are needed downstream. For a 10-parameter, all-optional listing tool, an agent has everything needed to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema coverage the baseline is 3, but the description adds real meaning for the two decision-driving parameters, giving dataset examples (GHCND, GSOM) and category examples (TEMP, PRCP) that clarify intent beyond the schema text. The remaining filters (startDate, endDate, stationId, locationId, sortField) are left entirely to the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ("List available data types") and immediately defines what a data type is with concrete labels (TMAX, TMIN, PRCP, SNOW). The two filtering modes (datasetId vs datacategoryId) distinguish it clearly from siblings like noaa_climate_list_datasets or noaa_climate_list_data_categories.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says to use this before noaa_climate_fetch_data when data type IDs are unknown, which names the alternative tool and the condition that selects it. It also routes between its own modes: datasetId to see what a dataset measures, datacategoryId (e.g. "TEMP") to see all types in a category.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
noaa_climate_list_location_categoriesList NOAA Climate Location CategoriesARead-onlyInspect
List the location categories that scope noaa_climate_find_locations — CITY, CLIM_DIV, CLIM_REG, CNTRY, CNTY, HYD_ACC, HYD_CAT, HYD_REG, HYD_SUB, ST, US_TERR, and ZIP. Call this first when you do not know which locationCategoryId to pass, including the hydrological categories needed to reach a basin or region. There are 12 categories in total. This endpoint takes pagination and sort only — NOAA CDO ignores dataset, location, station, and date filters here, so none are offered.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false. | |
| offset | No | Zero-based index of the first result to return for pagination. Defaults to 0. | |
| sortField | No | Sort results by this field. Optional. | |
| sortOrder | No | Sort direction. Optional; defaults to asc. |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies. |
| results | No | Matching location categories. |
| metadata | No | Pagination metadata. Present when the API returns it. |
| exhausted | No | True when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise. |
| totalCount | No | Total number of location categories before the page limit. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark it read-only and closed-world; the description adds non-obvious behavior: NOAA CDO ignores dataset/location/station/date filters here, so none are offered, and the endpoint accepts pagination and sort only. That extra context directly affects how an agent calls it and is beyond annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded and mostly efficient: purpose, when-to-use, and filter caveat appear early. The full 12-code enumeration and the following '12 categories in total' sentence are somewhat redundant but still useful for recognition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema, complete parameter descriptions, and annotations, the description supplies the remaining decision context: what the tool returns (category codes), when to call it before find_locations, and what filters are silently ignored. Nothing essential for correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and all four parameters are documented in the schema, so the baseline is 3. The description confirms 'pagination and sort only' and explains why filter parameters are absent, but it doesn't add syntax or meaning for limit/offset/sort beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List the location categories') and ties it directly to noaa_climate_find_locations as the consumer. It even enumerates the 12 category codes, so an agent can distinguish this lookup tool from the sibling location search tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says to call this first when the locationCategoryId is unknown, including hydrological cases, and names the sibling that consumes the result. It also states the endpoint accepts only pagination/sort and that dataset/location/station/date filters are ignored, which prevents incorrect calls.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
noaa_climate_search_storm_eventsSearch NOAA Storm EventsARead-onlyInspect
Search the NCEI Storm Events Database for one calendar year — tornadoes, hail, floods, hurricanes, winter storms, heat, and every other NWS Storm Data event type, with magnitude, direct and indirect casualties, property and crop damage, and narratives. This corpus carries discrete severe-weather events rather than CDO station observations, needs no token, and publishes one bulk file per year, so year is required. Filter by episodeId from a returned event, state (full NCEI name such as "FLORIDA", not "FL"), eventType (exact NWS label such as "Tornado", "Flash Flood", or "Hurricane (Typhoon)", case-insensitive), begin month, inclusive local-calendar startDate/endDate overlap, and minDamageInUsd. Date bounds exclude missing, invalid, or reversed source spans before damage accounting, totals, and paging; cross-year bounds still search only the selected year export. Damage retains its raw magnitude-suffixed cell and parsed dollar amount; unreported figures are omitted, and minDamageInUsd discloses how many unknown figures it excluded. Events reference distinct page-local episodeNarratives by episodeNarrativeRef; eventNarrative stays on each event, and rendered narratives preserve literal source text. Optional local ISO beginDate/endDate values can feed CDO date filters; raw NCEI date-time and timezone remain available. Source row order, limit/offset pagination, and filtered totalCount are preserved; appliedDateRange echoes supplied bounds.
| Name | Required | Description | Default |
|---|---|---|---|
| year | Yes | Calendar year to search (1950 through the current partial year). Required — NCEI publishes one file per year, so an unscoped search would download every year back to 1950. | |
| limit | No | Maximum events per page (1–100, default 50). Oversized positive integers are clamped to 100 with a notice; NOAA_CLAMP_LIMITS=false restores rejection above 100. | |
| month | No | Filter to events whose begin date falls in this month (1–12). Optional. | |
| state | No | Filter to this state or territory, written as the full name NCEI uses (e.g. "FLORIDA", "PUERTO RICO"), matched case-insensitively. Postal codes like "FL" match nothing. Optional. | |
| offset | No | Zero-based index of the first matching event to return. Defaults to 0. | |
| endDate | No | Inclusive local-calendar upper bound (YYYY-MM-DD): an event must begin on or before this date. Rows without both valid ordered endpoints are excluded. Cross-year intervals are allowed; only year selects the export. | |
| episodeId | No | Exact EPISODE_ID from a returned event. Surrounding whitespace is trimmed; blank means no filter. Leading zeros are significant. Keep year supplied. | |
| eventType | No | Filter to this NWS event type, matched case-insensitively against the exact label (e.g. "Tornado", "Hail", "Flash Flood", "Hurricane (Typhoon)"). A miss returns the labels present in that year. Optional. | |
| startDate | No | Inclusive local-calendar lower bound (YYYY-MM-DD): an event must end on or after this date. Rows without both valid ordered endpoints are excluded. Only the selected year export is searched. | |
| minDamageInUsd | No | Filter to events whose property damage parses to at least this many dollars. Excludes every row whose damage NCEI did not report — about a fifth of a recent year — since an unreported figure cannot be shown to clear the threshold. Optional. |
Output Schema
| Name | Required | Description |
|---|---|---|
| cap | No | The limit that was applied. Omitted otherwise. |
| year | No | The calendar year searched. |
| error | No | Present when the call failed. Absent on success. |
| shown | No | Events returned on this page. Omitted otherwise. |
| events | No | Matching events for the requested page, in the source file’s own row order. |
| notice | No | Clamp disclosure and guidance for truncation, no matches, or exhausted pages. Omitted when none applies. |
| exhausted | No | True when offset is past the end of a non-empty match set — the page is empty but matches exist. Omitted otherwise. |
| truncated | No | True when more matches exist beyond this page. Omitted otherwise. |
| sourceFile | No | The exact NCEI file this page was read from, including its `_c<publishDate>` suffix — the suffix changes whenever NCEI republishes a year. |
| totalCount | No | Events matching every filter across the whole year, before offset and limit. |
| scannedRowCount | No | Rows read from the source file, matched or not. Omitted when unavailable. |
| appliedDateRange | No | The applied inclusive local-calendar overlap interval. Omitted when neither bound was supplied; year still selects one export. |
| episodeNarratives | No | Each distinct episode narrative on this page, once; referenced by events[].episodeNarrativeRef. |
| excludedUnknownDamage | No | Rows that satisfied every other filter but were dropped by minDamageInUsd because NCEI reported no property-damage figure for them. Omitted when minDamageInUsd was not supplied. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the read-only and open-world annotations, the description discloses substantial behavior: no token is needed, the source is one file per year, date bounds exclude missing or reversed spans, cross-year bounds search only the selected year, unknown damage figures are omitted, and pagination plus appliedDateRange are preserved. This is unusually rich behavioral context for a read-only search tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The purpose and year requirement are front-loaded, and most sentences carry useful filtering or behavioral detail. The description is still a dense single paragraph, with some return-value detail that could be left to the output schema, so it is not maximally concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 10-parameter tool with an output schema, the description covers the required year scope, filtering semantics, missing-data handling, cross-year behavior, pagination, and return references. An agent has enough context to call it correctly without opening additional documentation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents every parameter, including state naming, eventType labels, date semantics, episodeId usage, and damage exclusions. The description reinforces a few filter behaviors but adds little parameter-level meaning beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: search the NCEI Storm Events Database for severe-weather event types with casualties, damage, and narratives. It also distinguishes the corpus from CDO station observations, which helps separate it from sibling climate-data tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explains that year is required because NCEI publishes one bulk file per year, and it positions this tool for discrete severe-weather events rather than CDO station observations. The alternative is described by category rather than by a named sibling tool, so it falls short of fully explicit when-versus-which guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
5 tool updates
- Changed
noaa_climate_fetch_data10 fields changed- added
Input schema / properties / stationId / items / descriptionAdded value: +"Station ID. Trims surrounding whitespace, uppercases IDs, and accepts bare 11-character GHCN aliases (USW00024233 → GHCND:USW00024233). Other namespaced IDs remain accepted." - added
Input schema / properties / stationId / items / patternAdded value: +"^\\s*(?:[A-Za-z]{2}[A-Za-z0-9]{9}|[^:\\s]+:[^\\s]+)\\s*$" - changed
Input schema / properties / units / descriptionPrevious value: -"Unit system for returned values. Without this parameter, GHCND returns raw tenths-of-unit integers (TMAX=256 = 25.6°C). Strongly recommended: pass metric (SI units) or standard (Fahrenheit/inches). Optional."New value: +"Request metric or standard conversion. Omission preserves datatype-specific raw values: GHCND TMAX/TMIN tenths °C, PRCP tenths mm, SNOW/SNWD whole mm; GSOM/GSOY temperature/precipitation °C/mm; NORMAL_* temperature normals tenths °F and precipitation normals hundredths inches; HPCP/QPCP hundredths inches. Examples are not complete unit metadata. Optional." - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `date_range_exceeded`: endDate is past the end of the calendar month 1 year after startDate for sub-daily/daily/radar datasets (GHCND, PRECIP_*, NORMAL_DLY, NORMAL_HLY, NEXRAD2, NEXRAD3), or 10 years after it for monthly/annual datasets (GSOM, GSOY, NORMAL_MLY, NORMAL_ANN). `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: Bad dataset ID, date format, or unknown station/location/datatype ID. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `date_range_exceeded`: endDate is past the end of the calendar month 1 year after startDate for sub-daily/daily/radar datasets (GHCND, PRECIP_*, NORMAL_DLY, NORMAL_HLY, NEXRAD2, NEXRAD3), or 10 years after it for monthly/annual datasets (GSOM, GSOY, NORMAL_MLY, NORMAL_ANN). `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: Bad dataset ID, date format, unknown station/location/datatype ID, or encoded observation query exceeding 4000 characters. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / notice / descriptionPrevious value: -"Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies."New value: +"Composed guidance for station ID normalization, page-limit adjustments, raw units, missing precipitation, GHCND quality-check failures, and empty or exhausted pages. Omitted when no guidance applies." - changed
Output schema / properties / results / items / properties / attributes / descriptionPrevious value: -"Quality flags and measurement attributes. Omitted when not provided."New value: +"Untouched upstream attributes. GHCND positions are measurement, quality, source, observation time; other datasets have their own layouts documented at https://www.ncei.noaa.gov/pub/data/cdo/documentation/." - added
Output schema / properties / results / items / properties / flagsAdded value: +{ + "additionalProperties": false, + "description": "Decoded GHCND attributes only. Absent trailing positions remain omitted; raw attributes and numeric values are retained.", + "properties": { + "measurement": { + "description": "GHCND measurement flag; an explicit blank is preserved.", + "type": "string" + }, + "observationTime": { + "description": "GHCND local observation time, preserving leading zeros and explicit blanks.", + "type": "string" + }, + "quality": { + "description": "GHCND quality flag; a nonblank code means a failed quality check. Explicit blanks are preserved.", + "type": "string" + }, + "source": { + "description": "GHCND source flag, including unknown codes and explicit blanks.", + "type": "string" + } + }, + "type": "object" +} - added
Output schema / properties / results / items / properties / missingAdded value: +{ + "const": true, + "description": "True for a documented PRECIP_HLY/HPCP or PRECIP_15/QPCP missing sentinel; value is omitted.", + "type": "boolean" +} - changed
Output schema / properties / results / items / properties / value / descriptionPrevious value: -"Observed value. Unit depends on the dataset and units parameter. For GHCND without units, this is a raw tenths-of-unit integer."New value: +"Observed value, omitted for identified missing precipitation. With units omitted, scale depends on datatype: GHCND TMAX/TMIN tenths °C, PRCP tenths mm, SNOW/SNWD whole mm; GSOM/GSOY temperature/precipitation °C/mm; NORMAL_* temperature normals tenths °F, precipitation normals hundredths inches; HPCP/QPCP hundredths inches. Examples are not universal conversion rules." - changed
Output schema / properties / results / items / requiredPrevious value: -[ - "date", - "datatype", - "station", - "value" -]New value: +[ + "date", + "datatype", + "station" +]
- Changed
noaa_climate_get_station3 fields changed- changed
Input schema / properties / stationId / descriptionPrevious value: -"Station ID to fetch (e.g., \"GHCND:USW00024233\", \"COOP:010008\"). Obtain from noaa_climate_find_stations."New value: +"Station ID to fetch (e.g., \"GHCND:USW00024233\", \"COOP:010008\"). Obtain from noaa_climate_find_stations. Trims surrounding whitespace, uppercases IDs, and accepts bare 11-character GHCN aliases (USW00024233 → GHCND:USW00024233). Other namespaced IDs remain accepted." - added
Input schema / properties / stationId / patternAdded value: +"^\\s*(?:[A-Za-z]{2}[A-Za-z0-9]{9}|[^:\\s]+:[^\\s]+)\\s*$" - added
Output schema / properties / noticeAdded value: +{ + "description": "Discloses station ID normalization when an alias was supplied.", + "type": "string" +}
- Changed
noaa_climate_list_data_categories3 fields changed- changed
Input schema / properties / stationId / descriptionPrevious value: -"Filter to categories available at this station ID. Optional."New value: +"Filter to categories available at this station ID. Optional. Trims surrounding whitespace, uppercases IDs, and accepts bare 11-character GHCN aliases (USW00024233 → GHCND:USW00024233). Other namespaced IDs remain accepted." - added
Input schema / properties / stationId / patternAdded value: +"^\\s*(?:[A-Za-z]{2}[A-Za-z0-9]{9}|[^:\\s]+:[^\\s]+)\\s*$" - changed
Output schema / properties / notice / descriptionPrevious value: -"Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies."New value: +"Station ID normalization, page-limit adjustment, and empty or exhausted-page guidance. Omitted when no guidance applies."
- Changed
noaa_climate_list_data_types3 fields changed- changed
Input schema / properties / stationId / descriptionPrevious value: -"Filter to data types available at this station ID. Optional."New value: +"Filter to data types available at this station ID. Optional. Trims surrounding whitespace, uppercases IDs, and accepts bare 11-character GHCN aliases (USW00024233 → GHCND:USW00024233). Other namespaced IDs remain accepted." - added
Input schema / properties / stationId / patternAdded value: +"^\\s*(?:[A-Za-z]{2}[A-Za-z0-9]{9}|[^:\\s]+:[^\\s]+)\\s*$" - changed
Output schema / properties / notice / descriptionPrevious value: -"Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies."New value: +"Station ID normalization, page-limit adjustment, and empty or exhausted-page guidance. Omitted when no guidance applies."
- Changed
noaa_climate_list_datasets3 fields changed- changed
Input schema / properties / stationId / descriptionPrevious value: -"Filter to datasets covering this station ID (e.g., \"GHCND:USW00024233\"). Optional."New value: +"Filter to datasets covering this station ID (e.g., \"GHCND:USW00024233\"). Optional. Trims surrounding whitespace, uppercases IDs, and accepts bare 11-character GHCN aliases (USW00024233 → GHCND:USW00024233). Other namespaced IDs remain accepted." - added
Input schema / properties / stationId / patternAdded value: +"^\\s*(?:[A-Za-z]{2}[A-Za-z0-9]{9}|[^:\\s]+:[^\\s]+)\\s*$" - changed
Output schema / properties / notice / descriptionPrevious value: -"Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies."New value: +"Station ID normalization, page-limit adjustment, and empty or exhausted-page guidance. Omitted when no guidance applies."
9 tool updates
- Changed
noaa_climate_fetch_data3 fields changed- changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum number of records to return (1–1000). Defaults to 25."New value: +"Maximum number of records to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false." - changed
Input schema / properties / limit / maximumPrevious value: -1000New value: +9007199254740991 - changed
Output schema / properties / notice / descriptionPrevious value: -"Guidance when no records were returned — echoes query parameters and suggests how to broaden."New value: +"Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies."
- Changed
noaa_climate_find_locations4 fields changed- changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum number of results to return (1–1000). Defaults to 25."New value: +"Maximum number of results to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false." - changed
Input schema / properties / limit / maximumPrevious value: -1000New value: +9007199254740991 - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: A filter parameter is not recognized by the NOAA CDO API (e.g., unknown datacategoryId or datasetId). `name_filter_requires_category`: nameContains was supplied without a locationCategoryId to scope the enumeration. `name_filter_category_too_large`: The requested locationCategoryId holds more locations than nameContains can enumerate. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: startDate is after endDate, or a filter parameter is not recognized by NOAA CDO (e.g., unknown datacategoryId or datasetId). `name_filter_requires_category`: nameContains was supplied without a locationCategoryId to scope the enumeration. `name_filter_category_too_large`: The requested locationCategoryId holds more locations than nameContains can enumerate. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / notice / descriptionPrevious value: -"Guidance when no locations matched — echoes applied filters and suggests how to broaden."New value: +"Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies."
- Changed
noaa_climate_find_stations7 fields changed- changed
Input schema / properties / extent / descriptionPrevious value: -"Bounding box filter as \"minLat,minLon,maxLat,maxLon\" (e.g., \"47.5,-122.4,47.7,-122.1\" for central Seattle). Optional."New value: +"Bounding box as \"minLat,minLon,maxLat,maxLon\": four finite signed decimal or scientific numbers with optional surrounding whitespace, latitude ±90 and longitude ±180. Equal coordinates are accepted; reversed axes return no matches, without wrapping. Example: \"47.5,-122.4,47.7,-122.1\". Optional." - removed
Input schema / properties / extent / minLengthRemoved value: -1 - added
Input schema / properties / extent / patternAdded value: +"^\\s*[+-]?(?:[0-9]+(?:\\.[0-9]*)?|\\.[0-9]+)(?:[eE][+-]?[0-9]+)?\\s*,\\s*[+-]?(?:[0-9]+(?:\\.[0-9]*)?|\\.[0-9]+)(?:[eE][+-]?[0-9]+)?\\s*,\\s*[+-]?(?:[0-9]+(?:\\.[0-9]*)?|\\.[0-9]+)(?:[eE][+-]?[0-9]+)?\\s*,\\s*[+-]?(?:[0-9]+(?:\\.[0-9]*)?|\\.[0-9]+)(?:[eE][+-]?[0-9]+)?\\s*$" - changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum number of results to return (1–1000). Defaults to 25."New value: +"Maximum number of results to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false." - changed
Input schema / properties / limit / maximumPrevious value: -1000New value: +9007199254740991 - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: A filter parameter is not recognized by the NOAA CDO API (e.g., unknown locationId or datacategoryId). Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: startDate is after endDate, or a filter parameter is not recognized by NOAA CDO (e.g., unknown locationId or datacategoryId). Other values are possible when a failure originates below the handler." - changed
Output schema / properties / notice / descriptionPrevious value: -"Guidance when no stations matched — echoes applied filters and suggests how to broaden."New value: +"Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies."
- Changed
noaa_climate_get_billion_dollar_disasters10 fields changed- changed
Input schema / properties / endYear / descriptionPrevious value: -"Latest year to include (1980 or later). NCEI publishes a year only once its assessment settles, so a year past coveredYears.last returns nothing rather than an error. Optional."New value: +"Latest year to include (1980 or later). The retired archive ends in 2024; years past coveredYears.last return no records rather than an error. Optional." - changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum number of disasters or years to return (1–100). Defaults to 50."New value: +"Maximum number of disasters or years to return (1–100). Defaults to 50. Larger positive integers are clamped to 100 with a notice unless NOAA_CLAMP_LIMITS=false." - changed
Input schema / properties / limit / maximumPrevious value: -100New value: +9007199254740991 - removed
Input schema / properties / state / minLengthRemoved value: -1 - added
Input schema / properties / state / patternAdded value: +"^\\s*[A-Za-z]{2}\\s*$" - changed
Output schema / properties / coveredYears / properties / last / descriptionPrevious value: -"Latest year present in the export — the last year NCEI has finished assessing, which trails the current calendar year."New value: +"Latest year present in this archived export. The retired product covers no years after 2024." - changed
Output schema / properties / disasters / items / properties / cpiAdjustedCostInUsd / descriptionPrevious value: -"Damage in whole US dollars, adjusted to present-day prices. This is the figure comparable across years."New value: +"Damage in whole US dollars with the CPI adjustment preserved from the archived NCEI export; not rebased to current prices." - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `invalid_state_code`: state was supplied in a form other than a two-letter US postal code. `unknown_state`: The state code is well formed but NCEI publishes no export under it. `invalid_year_range`: startYear is later than endYear, so the range can never match a record. `malformed_export`: The export downloaded but is not the expected table — no header row, no rows, missing columns, or no declared cost unit. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `unknown_state`: The state code is well formed but NCEI publishes no export under it. `invalid_year_range`: startYear is later than endYear, so the range can never match a record. `malformed_export`: The export downloaded but is not the expected table — no header row, no rows, missing columns, or no declared cost unit. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "invalid_state_code", - "unknown_state", - "invalid_year_range", - "malformed_export" -]New value: +[ + "unknown_state", + "invalid_year_range", + "malformed_export" +] - changed
Output schema / properties / notice / descriptionPrevious value: -"Guidance when nothing matched or the page ran past the end. Omitted otherwise."New value: +"Archive retirement and preserved CPI-adjustment disclosure, composed with any clamp, empty-page, exhaustion, or truncation guidance."
- Changed
noaa_climate_list_data_categories4 fields changed- changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum number of results to return (1–1000). Defaults to 25."New value: +"Maximum number of results to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false." - changed
Input schema / properties / limit / maximumPrevious value: -1000New value: +9007199254740991 - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: A filter parameter is not recognized by the NOAA CDO API (e.g., unknown datasetId). Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: startDate is after endDate, or a filter parameter is not recognized by NOAA CDO (e.g., unknown datasetId). Other values are possible when a failure originates below the handler." - changed
Output schema / properties / notice / descriptionPrevious value: -"Guidance when no data categories matched — echoes applied filters and suggests how to broaden."New value: +"Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies."
- Changed
noaa_climate_list_data_types4 fields changed- changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum number of results to return (1–1000). Defaults to 25."New value: +"Maximum number of results to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false." - changed
Input schema / properties / limit / maximumPrevious value: -1000New value: +9007199254740991 - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: A filter parameter is not recognized by the NOAA CDO API (e.g., unknown datacategoryId or datasetId). Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: startDate is after endDate, or a filter parameter is not recognized by NOAA CDO (e.g., unknown datacategoryId or datasetId). Other values are possible when a failure originates below the handler." - changed
Output schema / properties / notice / descriptionPrevious value: -"Guidance when no data types matched — echoes applied filters and suggests how to broaden."New value: +"Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies."
- Changed
noaa_climate_list_datasets7 fields changed- changed
Input schema / properties / endDate / descriptionPrevious value: -"Filter to datasets with data on or before this ISO date (YYYY-MM-DD). Optional."New value: +"Inclusive upper coverage bound: dataset mindate must be on or before this date. Applied locally before pagination. Optional." - changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum number of results to return (1–1000). Defaults to 25."New value: +"Maximum number of results to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false." - changed
Input schema / properties / limit / maximumPrevious value: -1000New value: +9007199254740991 - changed
Input schema / properties / startDate / descriptionPrevious value: -"Filter to datasets with data on or after this ISO date (YYYY-MM-DD). Optional."New value: +"Inclusive lower coverage bound: dataset maxdate must be on or after this date. Applied locally to the complete matching catalog before pagination. Optional." - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: Bad date format or unrecognized filter ID. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: Bad date format, startDate after endDate, or unrecognized filter ID. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / metadata / descriptionPrevious value: -"Pagination metadata. Present when the API returns it."New value: +"Pagination metadata. Synthesized for date-filtered views; otherwise present when the API returns it." - changed
Output schema / properties / notice / descriptionPrevious value: -"Guidance when no datasets matched — echoes applied filters and suggests how to broaden."New value: +"Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies."
- Changed
noaa_climate_list_location_categories3 fields changed- changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum number of results to return (1–1000). Defaults to 25."New value: +"Maximum number of results to return (1–1000). Defaults to 25. Larger positive integers are clamped to 1000 with a notice unless NOAA_CLAMP_LIMITS=false." - changed
Input schema / properties / limit / maximumPrevious value: -1000New value: +9007199254740991 - changed
Output schema / properties / notice / descriptionPrevious value: -"Guidance when no location categories were returned. Omitted otherwise."New value: +"Page-limit adjustment and empty or exhausted-page guidance. Omitted when no guidance applies."
- Changed
noaa_climate_search_storm_events9 fields changed- added
Input schema / properties / endDateAdded value: +{ + "description": "Inclusive local-calendar upper bound (YYYY-MM-DD): an event must begin on or before this date. Rows without both valid ordered endpoints are excluded. Cross-year intervals are allowed; only year selects the export.", + "format": "date", + "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$", + "type": "string" +} - added
Input schema / properties / episodeId / patternAdded value: +"^\\s*(?:\\d+\\s*)?$" - changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum number of events to return (1–100). Defaults to 50."New value: +"Maximum events per page (1–100, default 50). Oversized positive integers are clamped to 100 with a notice; NOAA_CLAMP_LIMITS=false restores rejection above 100." - changed
Input schema / properties / limit / maximumPrevious value: -100New value: +9007199254740991 - added
Input schema / properties / startDateAdded value: +{ + "description": "Inclusive local-calendar lower bound (YYYY-MM-DD): an event must end on or after this date. Rows without both valid ordered endpoints are excluded. Only the selected year export is searched.", + "format": "date", + "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$", + "type": "string" +} - added
Output schema / properties / appliedDateRangeAdded value: +{ + "additionalProperties": false, + "description": "The applied inclusive local-calendar overlap interval. Omitted when neither bound was supplied; year still selects one export.", + "properties": { + "endDate": { + "description": "Inclusive upper overlap bound supplied by the caller.", + "format": "date", + "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$", + "type": "string" + }, + "startDate": { + "description": "Inclusive lower overlap bound supplied by the caller.", + "format": "date", + "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$", + "type": "string" + } + }, + "type": "object" +} - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `year_unavailable`: The NCEI directory listing has no details file for the requested year. `service_unavailable`: The NCEI bulk file server would not hand back a usable file: the directory index is unreachable or carried no details files, the year bundle it names is gone, or the downloaded bundle did not decompress. `malformed_export`: The year decompressed but is not the expected table — required columns are missing, or the file carried no rows. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_date_range`: startDate is later than endDate. `year_unavailable`: The NCEI directory listing has no details file for the requested year. `service_unavailable`: The NCEI bulk file server would not hand back a usable file: the directory index is unreachable or carried no details files, the year bundle it names is gone, or the downloaded bundle did not decompress. `malformed_export`: The year decompressed but is not the expected table — required columns are missing, or the file carried no rows. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "year_unavailable", - "service_unavailable", - "malformed_export" -]New value: +[ + "invalid_date_range", + "year_unavailable", + "service_unavailable", + "malformed_export" +] - changed
Output schema / properties / notice / descriptionPrevious value: -"Guidance when nothing matched or the page ran past the end. Omitted otherwise."New value: +"Clamp disclosure and guidance for truncation, no matches, or exhausted pages. Omitted when none applies."
8 tool updates
- Changed
noaa_climate_fetch_data1 field changed- changed
Output schema / properties / metadata / properties / resultset / properties / offset / descriptionPrevious value: -"1-based starting index of this page as returned by the NOAA CDO API."New value: +"Zero-based starting index of this page, echoing the requested offset."
- Changed
noaa_climate_find_locations1 field changed- changed
Output schema / properties / metadata / properties / resultset / properties / offset / descriptionPrevious value: -"Starting index of this page: 1-based as returned by the NOAA CDO API, or the zero-based offset you supplied when appliedNameFilter is present."New value: +"Zero-based starting index of this page, echoing the requested offset."
- Changed
noaa_climate_find_stations1 field changed- changed
Output schema / properties / metadata / properties / resultset / properties / offset / descriptionPrevious value: -"1-based starting index of this page as returned by the NOAA CDO API."New value: +"Zero-based starting index of this page, echoing the requested offset."
- Changed
noaa_climate_list_data_categories1 field changed- changed
Output schema / properties / metadata / properties / resultset / properties / offset / descriptionPrevious value: -"1-based starting index of this page as returned by the NOAA CDO API."New value: +"Zero-based starting index of this page, echoing the requested offset."
- Changed
noaa_climate_list_data_types1 field changed- changed
Output schema / properties / metadata / properties / resultset / properties / offset / descriptionPrevious value: -"1-based starting index of this page as returned by the NOAA CDO API."New value: +"Zero-based starting index of this page, echoing the requested offset."
- Changed
noaa_climate_list_datasets1 field changed- changed
Output schema / properties / metadata / properties / resultset / properties / offset / descriptionPrevious value: -"1-based starting index of this page as returned by the NOAA CDO API."New value: +"Zero-based starting index of this page, echoing the requested offset."
- Changed
noaa_climate_list_location_categories1 field changed- changed
Output schema / properties / metadata / properties / resultset / properties / offset / descriptionPrevious value: -"1-based starting index of this page as returned by the NOAA CDO API."New value: +"Zero-based starting index of this page, echoing the requested offset."
- Changed
noaa_climate_search_storm_events7 fields changed- added
Input schema / properties / episodeIdAdded value: +{ + "description": "Exact EPISODE_ID from a returned event. Surrounding whitespace is trimmed; blank means no filter. Leading zeros are significant. Keep year supplied.", + "type": "string" +} - changed
Output schema / anyOfPrevious value: -[ - { - "not": { - "required": [ - "error" - ] - }, - "required": [ - "year", - "sourceFile", - "events", - "totalCount" - ] - }, - { - "required": [ - "error" - ] - } -]New value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "year", + "sourceFile", + "events", + "episodeNarratives", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / episodeNarrativesAdded value: +{ + "description": "Each distinct episode narrative on this page, once; referenced by events[].episodeNarrativeRef.", + "items": { + "additionalProperties": false, + "description": "One distinct episode narrative on this page.", + "properties": { + "ref": { + "description": "Page-local narrative reference, e.g. n1.", + "type": "string" + }, + "text": { + "description": "Distinct nonblank episode narrative text, preserved from the service.", + "type": "string" + } + }, + "required": [ + "ref", + "text" + ], + "type": "object" + }, + "type": "array" +} - added
Output schema / properties / events / items / properties / beginDateAdded value: +{ + "description": "Local ISO calendar start date (YYYY-MM-DD), usable with CDO date filters. Omitted when source components are missing or invalid.", + "type": "string" +} - added
Output schema / properties / events / items / properties / endDateAdded value: +{ + "description": "Local ISO calendar end date (YYYY-MM-DD). Omitted when source components are missing or invalid; not a UTC conversion.", + "type": "string" +} - removed
Output schema / properties / events / items / properties / episodeNarrativeRemoved value: -{ - "description": "Narrative for the whole storm episode, shared by every event in it. Omitted when absent.", - "type": "string" -} - added
Output schema / properties / events / items / properties / episodeNarrativeRefAdded value: +{ + "description": "Reference to this page’s episodeNarratives text. Omitted when no narrative was reported.", + "type": "string" +}
10 tool updates
- Changed
noaa_climate_fetch_data6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "results", + "totalCount", + "effectiveQuery" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `date_range_exceeded`: endDate is past the end of the calendar month 1 year after startDate for sub-daily/daily/radar datasets (GHCND, PRECIP_*, NORMAL_DLY, NORMAL_HLY, NEXRAD2, NEXRAD3), or 10 years after it for monthly/annual datasets (GSOM, GSOY, NORMAL_MLY, NORMAL_ANN). `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: Bad dataset ID, date format, or unknown station/location/datatype ID. Other values are possible when a failure originates below the handler.", + "examples": [ + "service_unavailable", + "rate_limited", + "date_range_exceeded", + "upstream_auth_failed", + "validation_error" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "results", - "totalCount", - "effectiveQuery" -]
- Changed
noaa_climate_find_locations6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "results", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: A filter parameter is not recognized by the NOAA CDO API (e.g., unknown datacategoryId or datasetId). `name_filter_requires_category`: nameContains was supplied without a locationCategoryId to scope the enumeration. `name_filter_category_too_large`: The requested locationCategoryId holds more locations than nameContains can enumerate. Other values are possible when a failure originates below the handler.", + "examples": [ + "service_unavailable", + "rate_limited", + "upstream_auth_failed", + "validation_error", + "name_filter_requires_category", + "name_filter_category_too_large" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "results", - "totalCount" -]
- Changed
noaa_climate_find_stations6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "results", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: A filter parameter is not recognized by the NOAA CDO API (e.g., unknown locationId or datacategoryId). Other values are possible when a failure originates below the handler.", + "examples": [ + "service_unavailable", + "rate_limited", + "upstream_auth_failed", + "validation_error" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "results", - "totalCount" -]
- Changed
noaa_climate_get_billion_dollar_disasters6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "mode", + "scope", + "sourceFile", + "declaredCostUnit", + "coveredYears", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `invalid_state_code`: state was supplied in a form other than a two-letter US postal code. `unknown_state`: The state code is well formed but NCEI publishes no export under it. `invalid_year_range`: startYear is later than endYear, so the range can never match a record. `malformed_export`: The export downloaded but is not the expected table — no header row, no rows, missing columns, or no declared cost unit. Other values are possible when a failure originates below the handler.", + "examples": [ + "invalid_state_code", + "unknown_state", + "invalid_year_range", + "malformed_export" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "mode", - "scope", - "sourceFile", - "declaredCostUnit", - "coveredYears", - "totalCount" -]
- Changed
noaa_climate_get_station6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "id", + "name" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Station ID format is valid but no station exists with that ID. `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. Other values are possible when a failure originates below the handler.", + "examples": [ + "not_found", + "service_unavailable", + "rate_limited", + "upstream_auth_failed" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "id", - "name" -]
- Changed
noaa_climate_list_data_categories6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "results", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: A filter parameter is not recognized by the NOAA CDO API (e.g., unknown datasetId). Other values are possible when a failure originates below the handler.", + "examples": [ + "service_unavailable", + "rate_limited", + "upstream_auth_failed", + "validation_error" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "results", - "totalCount" -]
- Changed
noaa_climate_list_data_types6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "results", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: A filter parameter is not recognized by the NOAA CDO API (e.g., unknown datacategoryId or datasetId). Other values are possible when a failure originates below the handler.", + "examples": [ + "service_unavailable", + "rate_limited", + "upstream_auth_failed", + "validation_error" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "results", - "totalCount" -]
- Changed
noaa_climate_list_datasets6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "results", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: Bad date format or unrecognized filter ID. Other values are possible when a failure originates below the handler.", + "examples": [ + "service_unavailable", + "rate_limited", + "upstream_auth_failed", + "validation_error" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "results", - "totalCount" -]
- Changed
noaa_climate_list_location_categories6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "results", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `service_unavailable`: NOAA CDO API is unreachable or returning errors. `rate_limited`: NOAA CDO throttled the request — the configured token went over its rate limit. `upstream_auth_failed`: NOAA CDO rejected the API token this server is configured with. `validation_error`: A pagination or sort parameter is not recognized by the NOAA CDO API. Other values are possible when a failure originates below the handler.", + "examples": [ + "service_unavailable", + "rate_limited", + "upstream_auth_failed", + "validation_error" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "results", - "totalCount" -]
- Changed
noaa_climate_search_storm_events6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "year", + "sourceFile", + "events", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `year_unavailable`: The NCEI directory listing has no details file for the requested year. `service_unavailable`: The NCEI bulk file server would not hand back a usable file: the directory index is unreachable or carried no details files, the year bundle it names is gone, or the downloaded bundle did not decompress. `malformed_export`: The year decompressed but is not the expected table — required columns are missing, or the file carried no rows. Other values are possible when a failure originates below the handler.", + "examples": [ + "year_unavailable", + "service_unavailable", + "malformed_export" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "year", - "sourceFile", - "events", - "totalCount" -]
1 tool update
- Added
noaa_climate_get_billion_dollar_disasters
1 tool update
- Added
noaa_climate_search_storm_events
6 tool updates
- Changed
noaa_climate_fetch_data3 fields changed- changed
Input schema / properties / datasetId / descriptionPrevious value: -"Dataset ID to query (e.g., GHCND for daily data, GSOM for monthly, GSOY for annual, NORMAL_DLY/MLY/ANN/HLY for 1981–2010 climate normals). Determines date range limit: GHCND/PRECIP_*/NORMAL_DLY/NORMAL_HLY allow 1-year max per request; GSOM/GSOY/NORMAL_MLY/NORMAL_ANN allow 10-year max."New value: +"Dataset ID to query (e.g., GHCND for daily data, GSOM for monthly, GSOY for annual, NORMAL_DLY/MLY/ANN/HLY for 1981–2010 climate normals, NEXRAD2/NEXRAD3 for weather radar). Determines date range limit: GHCND/PRECIP_*/NORMAL_DLY/NORMAL_HLY/NEXRAD2/NEXRAD3 allow 1-year max per request; GSOM/GSOY/NORMAL_MLY/NORMAL_ANN allow 10-year max." - changed
Input schema / properties / endDate / descriptionPrevious value: -"End date for observations (YYYY-MM-DD). Must be within 1 year of startDate for sub-daily/daily datasets (GHCND, PRECIP_15, PRECIP_HLY, NORMAL_DLY, NORMAL_HLY) or within 10 years for monthly/annual datasets (GSOM, GSOY, NORMAL_MLY, NORMAL_ANN). For any NORMAL_* dataset use 2010-12-31."New value: +"End date for observations (YYYY-MM-DD). Must be within 1 year of startDate for sub-daily/daily/radar datasets (GHCND, PRECIP_15, PRECIP_HLY, NORMAL_DLY, NORMAL_HLY, NEXRAD2, NEXRAD3) or within 10 years for monthly/annual datasets (GSOM, GSOY, NORMAL_MLY, NORMAL_ANN) — measured to the end of the calendar month that many years after startDate, so a full calendar year (2024-01-01 to 2024-12-31) always fits. For any NORMAL_* dataset use 2010-12-31." - changed
Input schema / properties / stationId / descriptionPrevious value: -"One or more station IDs to filter by (e.g., [\"GHCND:USC00450974\"]). Obtain from noaa_climate_find_stations. Multiple IDs return comparative readings across stations. Optional."New value: +"One or more station IDs to filter by (e.g., [\"GHCND:USW00024233\"]). Obtain from noaa_climate_find_stations. Multiple IDs return comparative readings across stations. Optional."
- Changed
noaa_climate_find_locations6 fields changed- changed
Input schema / properties / locationCategoryId / descriptionPrevious value: -"Category filter. Use ST for states (51 entries), CNTY for counties, CITY for cities (large set — thousands of entries), CNTRY for countries, ZIP for zip codes, CLIM_REG for NOAA climate regions, CLIM_DIV for climate divisions, HYD_ACC/HYD_CAT/HYD_REG/HYD_SUB for hydrological categories. Optional — omit to return all location types."New value: +"Category filter. Use ST for states (51 entries), CNTY for counties, CITY for cities (large set — thousands of entries), CNTRY for countries, ZIP for zip codes, US_TERR for US territories, CLIM_REG for NOAA climate regions, CLIM_DIV for climate divisions, HYD_ACC/HYD_CAT/HYD_REG/HYD_SUB for hydrological categories. Call noaa_climate_list_location_categories when you do not know which category to use — it returns the authoritative set. Optional — omit to return all location types." - added
Input schema / properties / nameContainsAdded value: +{ + "description": "Case-insensitive substring match on the location name. The CDO API has no name parameter, so this server applies the match itself, across the whole category rather than one page — which bounds it to a category holding at most 4000 locations. Requires locationCategoryId; adding datasetId or datacategoryId narrows a category that is otherwise too large. Example: locationCategoryId=\"CITY\" with nameContains=\"seattle\". Optional.", + "minLength": 1, + "type": "string" +} - added
Output schema / properties / appliedNameFilterAdded value: +{ + "description": "The nameContains value this response was filtered by. Present only when nameContains was supplied; every count below then describes the filtered set, not the whole category.", + "type": "string" +} - changed
Output schema / properties / metadata / properties / resultset / properties / count / descriptionPrevious value: -"Total number of matching locations."New value: +"Total number of matching locations — the post-filter match count when appliedNameFilter is present." - changed
Output schema / properties / metadata / properties / resultset / properties / offset / descriptionPrevious value: -"1-based starting index of this page as returned by the NOAA CDO API."New value: +"Starting index of this page: 1-based as returned by the NOAA CDO API, or the zero-based offset you supplied when appliedNameFilter is present." - changed
Output schema / properties / results / items / properties / id / descriptionPrevious value: -"Location ID (e.g., FIPS:37, CITY:US530031, ZIP:98101)."New value: +"Location ID (e.g., FIPS:37, CITY:US530018, ZIP:98101)."
- Changed
noaa_climate_find_stations2 fields changed- changed
Input schema / properties / locationId / descriptionPrevious value: -"Filter to stations within this location ID (e.g., \"FIPS:37\" for NC, \"CITY:US530031\" for Seattle). Obtain from noaa_climate_find_locations. Optional."New value: +"Filter to stations within this location ID (e.g., \"FIPS:37\" for NC, \"CITY:US530018\" for Seattle). Obtain from noaa_climate_find_locations. Optional." - changed
Output schema / properties / results / items / properties / id / descriptionPrevious value: -"Station ID (e.g., GHCND:USC00450974, COOP:010008)."New value: +"Station ID (e.g., GHCND:USW00024233, COOP:010008)."
- Changed
noaa_climate_get_station1 field changed- changed
Input schema / properties / stationId / descriptionPrevious value: -"Station ID to fetch (e.g., \"GHCND:USC00450974\", \"COOP:010008\"). Obtain from noaa_climate_find_stations."New value: +"Station ID to fetch (e.g., \"GHCND:USW00024233\", \"COOP:010008\"). Obtain from noaa_climate_find_stations."
- Changed
noaa_climate_list_datasets1 field changed- changed
Input schema / properties / stationId / descriptionPrevious value: -"Filter to datasets covering this station ID (e.g., \"GHCND:USC00450974\"). Optional."New value: +"Filter to datasets covering this station ID (e.g., \"GHCND:USW00024233\"). Optional."
- Added
noaa_climate_list_location_categories
6 tool updates
- Changed
noaa_climate_fetch_data9 fields changed- added
Input schema / properties / datatypeId / items / minLengthAdded value: +1 - added
Input schema / properties / datatypeId / minItemsAdded value: +1 - added
Input schema / properties / endDate / patternAdded value: +"^(?:\\d{4}(?:0[1-9]|1[0-2])(?:0[1-9]|[12]\\d|3[01])|\\d{4}-(?:0?[1-9]|1[0-2])-(?:0?[1-9]|[12]\\d|3[01])(?:T(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?)?)$" - added
Input schema / properties / locationId / items / minLengthAdded value: +1 - added
Input schema / properties / locationId / minItemsAdded value: +1 - added
Input schema / properties / startDate / patternAdded value: +"^(?:\\d{4}(?:0[1-9]|1[0-2])(?:0[1-9]|[12]\\d|3[01])|\\d{4}-(?:0?[1-9]|1[0-2])-(?:0?[1-9]|[12]\\d|3[01])(?:T(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?)?)$" - added
Input schema / properties / stationId / items / minLengthAdded value: +1 - added
Input schema / properties / stationId / minItemsAdded value: +1 - added
Output schema / properties / exhaustedAdded value: +{ + "description": "True when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise.", + "type": "boolean" +}
- Changed
noaa_climate_find_locations6 fields changed- added
Input schema / properties / datacategoryId / minLengthAdded value: +1 - added
Input schema / properties / datasetId / minLengthAdded value: +1 - added
Input schema / properties / endDate / patternAdded value: +"^(?:\\d{4}(?:0[1-9]|1[0-2])(?:0[1-9]|[12]\\d|3[01])|\\d{4}-(?:0?[1-9]|1[0-2])-(?:0?[1-9]|[12]\\d|3[01])(?:T(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?)?)$" - added
Input schema / properties / locationCategoryId / minLengthAdded value: +1 - added
Input schema / properties / startDate / patternAdded value: +"^(?:\\d{4}(?:0[1-9]|1[0-2])(?:0[1-9]|[12]\\d|3[01])|\\d{4}-(?:0?[1-9]|1[0-2])-(?:0?[1-9]|[12]\\d|3[01])(?:T(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?)?)$" - added
Output schema / properties / exhaustedAdded value: +{ + "description": "True when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise.", + "type": "boolean" +}
- Changed
noaa_climate_find_stations9 fields changed- added
Input schema / properties / datacategoryId / minLengthAdded value: +1 - added
Input schema / properties / datasetId / minLengthAdded value: +1 - added
Input schema / properties / datatypeId / items / minLengthAdded value: +1 - added
Input schema / properties / datatypeId / minItemsAdded value: +1 - added
Input schema / properties / endDate / patternAdded value: +"^(?:\\d{4}(?:0[1-9]|1[0-2])(?:0[1-9]|[12]\\d|3[01])|\\d{4}-(?:0?[1-9]|1[0-2])-(?:0?[1-9]|[12]\\d|3[01])(?:T(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?)?)$" - added
Input schema / properties / extent / minLengthAdded value: +1 - added
Input schema / properties / locationId / minLengthAdded value: +1 - added
Input schema / properties / startDate / patternAdded value: +"^(?:\\d{4}(?:0[1-9]|1[0-2])(?:0[1-9]|[12]\\d|3[01])|\\d{4}-(?:0?[1-9]|1[0-2])-(?:0?[1-9]|[12]\\d|3[01])(?:T(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?)?)$" - added
Output schema / properties / exhaustedAdded value: +{ + "description": "True when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise.", + "type": "boolean" +}
- Changed
noaa_climate_list_data_categories6 fields changed- added
Input schema / properties / datasetId / minLengthAdded value: +1 - added
Input schema / properties / endDate / patternAdded value: +"^(?:\\d{4}(?:0[1-9]|1[0-2])(?:0[1-9]|[12]\\d|3[01])|\\d{4}-(?:0?[1-9]|1[0-2])-(?:0?[1-9]|[12]\\d|3[01])(?:T(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?)?)$" - added
Input schema / properties / locationId / minLengthAdded value: +1 - added
Input schema / properties / startDate / patternAdded value: +"^(?:\\d{4}(?:0[1-9]|1[0-2])(?:0[1-9]|[12]\\d|3[01])|\\d{4}-(?:0?[1-9]|1[0-2])-(?:0?[1-9]|[12]\\d|3[01])(?:T(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?)?)$" - added
Input schema / properties / stationId / minLengthAdded value: +1 - added
Output schema / properties / exhaustedAdded value: +{ + "description": "True when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise.", + "type": "boolean" +}
- Changed
noaa_climate_list_data_types7 fields changed- added
Input schema / properties / datacategoryId / minLengthAdded value: +1 - added
Input schema / properties / datasetId / minLengthAdded value: +1 - added
Input schema / properties / endDate / patternAdded value: +"^(?:\\d{4}(?:0[1-9]|1[0-2])(?:0[1-9]|[12]\\d|3[01])|\\d{4}-(?:0?[1-9]|1[0-2])-(?:0?[1-9]|[12]\\d|3[01])(?:T(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?)?)$" - added
Input schema / properties / locationId / minLengthAdded value: +1 - added
Input schema / properties / startDate / patternAdded value: +"^(?:\\d{4}(?:0[1-9]|1[0-2])(?:0[1-9]|[12]\\d|3[01])|\\d{4}-(?:0?[1-9]|1[0-2])-(?:0?[1-9]|[12]\\d|3[01])(?:T(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?)?)$" - added
Input schema / properties / stationId / minLengthAdded value: +1 - added
Output schema / properties / exhaustedAdded value: +{ + "description": "True when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise.", + "type": "boolean" +}
- Changed
noaa_climate_list_datasets7 fields changed- added
Input schema / properties / datatypeId / items / minLengthAdded value: +1 - added
Input schema / properties / datatypeId / minItemsAdded value: +1 - added
Input schema / properties / endDate / patternAdded value: +"^(?:\\d{4}(?:0[1-9]|1[0-2])(?:0[1-9]|[12]\\d|3[01])|\\d{4}-(?:0?[1-9]|1[0-2])-(?:0?[1-9]|[12]\\d|3[01])(?:T(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?)?)$" - added
Input schema / properties / locationId / minLengthAdded value: +1 - added
Input schema / properties / startDate / patternAdded value: +"^(?:\\d{4}(?:0[1-9]|1[0-2])(?:0[1-9]|[12]\\d|3[01])|\\d{4}-(?:0?[1-9]|1[0-2])-(?:0?[1-9]|[12]\\d|3[01])(?:T(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?)?)$" - added
Input schema / properties / stationId / minLengthAdded value: +1 - added
Output schema / properties / exhaustedAdded value: +{ + "description": "True when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise.", + "type": "boolean" +}
7 tool updates
- First observed
noaa_climate_fetch_data - First observed
noaa_climate_find_locations - First observed
noaa_climate_find_stations - First observed
noaa_climate_get_station - First observed
noaa_climate_list_data_categories - First observed
noaa_climate_list_data_types - First observed
noaa_climate_list_datasets
Related MCP Connectors
Search NOAA CDO stations and datasets, fetch historical weather observations.
Find NOAA tide stations and NDBC buoys, fetch tide predictions, currents, and live conditions.
Find air-quality stations and read pollutant observations from government monitors via OpenAQ v3.
Historical weather and climate: 100+ years of station data, normals, extremes, and trends.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access NOAA's national climate archive—GHCN-Daily observations, station search, and dataset catalog—without an API key.355 npmMIT
- AlicenseNot gradedqualityAmaintenanceGet US weather forecasts, active alerts, and current observations via the National Weather Service API.605 npm1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceFind NOAA tide stations and NDBC buoys, fetch tide predictions, water levels, tidal currents, and live buoy conditions via MCP.908 npm1Apache 2.0
- AlicenseNot gradedqualityFmaintenanceProvides access to NOAA National Weather Service forecasts and alerts. Enables finding weather observation stations in US states via the get_stations tool.3 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.