noaa-climate-mcp-server

Get NOAA Climate Station

noaa_climate_get_station

Read-only

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.

Input Schema

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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 3, 2026

changedInput schema / properties / stationId / description

Previous 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."

addedInput schema / properties / stationId / pattern

Added value: +"^\\s*(?:[A-Za-z]{2}[A-Za-z0-9]{9}|[^:\\s]+:[^\\s]+)\\s*$"

addedOutput schema / properties / notice

Added value: +{
+  "description": "Discloses station ID normalization when an alias was supplied.",
+  "type": "string"
+}

Changed6 schema fields changedAug 25, 2026

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": [
+      "id",
+      "name"
+    ]
+  },
+  {
+    "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: `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"
+}

removedOutput schema / required
```
Removed value: -[
-  "id",
-  "name"
-]
```

Changed1 schema field changedAug 18, 2026

changedInput schema / properties / stationId / description

Previous 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."

First observedJun 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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.

Conciseness5/5

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.

Completeness4/5

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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents 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.

Purpose5/5

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.

Usage Guidelines4/5

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.

All noaa-climate-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.