Skip to main content
Glama

noaa-climate-mcp-server

Fetch NOAA Climate Observation Data

noaa_climate_fetch_data
Read-only

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.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum 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.
unitsNoRequest 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.
offsetNoZero-based index of the first record to return for pagination. Defaults to 0.
endDateYesEnd 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.
datasetIdYesDataset 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.
sortFieldNoSort results by this field. Optional.
sortOrderNoSort direction. Optional; defaults to asc.
startDateYesStart 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.
stationIdNoOne 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.
datatypeIdNoOne 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.
locationIdNoOne 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.
includemetadataNoInclude pagination metadata in the response. Defaults to true.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoComposed 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.
resultsNoFlat array of observation records sorted by date by default.
metadataNoPagination metadata. Present when includemetadata=true.
exhaustedNoTrue when the requested offset is past the end of a non-empty result set — the page is empty but matches exist. Omitted otherwise.
totalCountNoTotal number of matching observation records before the page limit.
effectiveQueryNoSummary of the effective query: dataset, date range, units, and any station/location/datatype filters applied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / stationId / items / description
      Added value: +"Station ID. Trims surrounding whitespace, uppercases IDs, and accepts bare 11-character GHCN aliases (USW00024233 → GHCND:USW00024233). Other namespaced IDs remain accepted."
    • addedInput schema / properties / stationId / items / pattern
      Added value: +"^\\s*(?:[A-Za-z]{2}[A-Za-z0-9]{9}|[^:\\s]+:[^\\s]+)\\s*$"
    • changedInput schema / properties / units / description
      Previous 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."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous 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."
    • changedOutput schema / properties / notice / description
      Previous 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."
    • changedOutput schema / properties / results / items / properties / attributes / description
      Previous 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/."
    • addedOutput schema / properties / results / items / properties / flags
      Added 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"
      +}
    • addedOutput schema / properties / results / items / properties / missing
      Added value: +{
      +  "const": true,
      +  "description": "True for a documented PRECIP_HLY/HPCP or PRECIP_15/QPCP missing sentinel; value is omitted.",
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / results / items / properties / value / description
      Previous 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."
    • changedOutput schema / properties / results / items / required
      Previous value: -[
      -  "date",
      -  "datatype",
      -  "station",
      -  "value"
      -]New value: +[
      +  "date",
      +  "datatype",
      +  "station"
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous 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."
    • changedInput schema / properties / limit / maximum
      Previous value: -1000New value: +9007199254740991
    • changedOutput schema / properties / notice / description
      Previous 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."
  3. Changed1 schema field changed
    • changedOutput schema / properties / metadata / properties / resultset / properties / offset / description
      Previous 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."
  4. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "results",
      +      "totalCount",
      +      "effectiveQuery"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / error
      Added 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"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "results",
      -  "totalCount",
      -  "effectiveQuery"
      -]
  5. Changed3 schema fields changed
    • changedInput schema / properties / datasetId / description
      Previous 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."
    • changedInput schema / properties / endDate / description
      Previous 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."
    • changedInput schema / properties / stationId / description
      Previous 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."
  6. Changed9 schema fields changed
    • addedInput schema / properties / datatypeId / items / minLength
      Added value: +1
    • addedInput schema / properties / datatypeId / minItems
      Added value: +1
    • addedInput schema / properties / endDate / pattern
      Added 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+)?)?)$"
    • addedInput schema / properties / locationId / items / minLength
      Added value: +1
    • addedInput schema / properties / locationId / minItems
      Added value: +1
    • addedInput schema / properties / startDate / pattern
      Added 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+)?)?)$"
    • addedInput schema / properties / stationId / items / minLength
      Added value: +1
    • addedInput schema / properties / stationId / minItems
      Added value: +1
    • addedOutput schema / properties / exhausted
      Added 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. First observed

TDQS

A3.9/5.0
Behavior4/5

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.

Conciseness4/5

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.

Completeness4/5

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.

Parameters3/5

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.

Purpose4/5

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.

Usage Guidelines4/5

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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.