noaa-spaceweather-mcp-server

Get Space Weather Alerts

noaa_spaceweather_get_alerts

Read-onlyIdempotent

Active SWPC alerts, watches, and warnings — parsed into structured records with product type, NOAA scale and level, issue time, validity window, and plain text. Covers geomagnetic storms, radio blackouts, and radiation storms. With active_only=false, also returns informational summaries, expired notices, and cancellations. max_age_hours controls how far back to look (default 48 h); the SWPC feed keeps all historical records and has no built-in expiry.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`active_only`	No	When true (default), return only in-force Warnings, Watches, and Alerts; exclude Summaries, Other, expired products, and cancellation notices. Set false to return all products, including cancellations (flagged by the cancelled field).
`max_age_hours`	No	Maximum age of alerts to return, in hours (default 48). The SWPC feed retains all historical records — this window prevents returning weeks of historical notices as "active."

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`alerts`	No	Matching SWPC alert/watch/warning records.
`notice`	No	Status notice when no alerts are active.
`fetchedAt`	No	ISO 8601 timestamp of when this data was fetched.
`totalCount`	No	Count of records in the alerts array.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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": [
+      "alerts",
+      "totalCount",
+      "fetchedAt"
+    ]
+  },
+  {
+    "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: `feed_unavailable`: SWPC endpoint returns non-OK status or times out after retries. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "feed_unavailable"
+          ],
+          "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: -[
-  "alerts",
-  "totalCount",
-  "fetchedAt"
-]

Changed6 schema fields changedJul 16, 2026

changedInput schema / properties / active_only / description

Previous value: -"When true (default), return only Warnings, Watches, and Alerts; exclude Summaries and Other. Set false to return all products."New value: +"When true (default), return only in-force Warnings, Watches, and Alerts; exclude Summaries, Other, expired products, and cancellation notices. Set false to return all products, including cancellations (flagged by the cancelled field)."

addedOutput schema / properties / alerts / items / properties / cancelled

Added value: +{
+  "description": "True when this record cancels a previously issued product (\"CANCEL WARNING:\"/\"CANCEL ALERT:\" headline) rather than being in force. Always false when active_only=true, which excludes cancellations; set active_only=false to see them.",
+  "type": "boolean"
+}

changedOutput schema / properties / alerts / items / properties / level / description

Previous value: -"Numeric severity level from the product code (0 when not applicable)."New value: +"NOAA scale level 0–5, read from the scale stated in the message body. 0 means the product states no NOAA scale (e.g. a K4 warning, below the G-scale; or a radio-burst alert, outside the scales) — not a severity of zero. See noaaScale for the scale letter."

addedOutput schema / properties / alerts / items / properties / noaaScale

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "NOAA scale stated in the message body, e.g. \"G1\", \"R2\", \"S1\"; null when the product states none."
+}

changedOutput schema / properties / alerts / items / properties / phenomenon / description

Previous value: -"Short phenomenon name, e.g. \"Geomagnetic\", \"Radio Blackout\", \"Solar Radiation\"."New value: +"Short phenomenon name derived from the body's NOAA scale letter, e.g. \"Geomagnetic\", \"Radio Blackout\", \"Solar Radiation\"."

changedOutput schema / properties / alerts / items / required

Previous value: -[
-  "productId",
-  "messageCode",
-  "productType",
-  "level",
-  "phenomenon",
-  "issueDatetime",
-  "validFrom",
-  "validTo",
-  "message"
-]New value: +[
+  "productId",
+  "messageCode",
+  "productType",
+  "level",
+  "noaaScale",
+  "cancelled",
+  "phenomenon",
+  "issueDatetime",
+  "validFrom",
+  "validTo",
+  "message"
+]

Changed3 schema fields changedJul 1, 2026

addedOutput schema / properties / alerts / items / properties / messageCode

Added value: +{
+  "description": "Full SWPC \"Space Weather Message Code\" parsed from the message body, e.g. \"WARK04\", \"ALTEF3\" — the code that drives product type, phenomenon, and level.",
+  "type": "string"
+}

changedOutput schema / properties / alerts / items / properties / productId / description

Previous value: -"SWPC product code, e.g. \"WARK04\", \"ALTK07\"."New value: +"Short SWPC feed product ID, e.g. \"K04W\", \"EF3A\". See messageCode for the full code."

changedOutput schema / properties / alerts / items / required

Previous value: -[
-  "productId",
-  "productType",
-  "level",
-  "phenomenon",
-  "issueDatetime",
-  "validFrom",
-  "validTo",
-  "message"
-]New value: +[
+  "productId",
+  "messageCode",
+  "productType",
+  "level",
+  "phenomenon",
+  "issueDatetime",
+  "validFrom",
+  "validTo",
+  "message"
+]

Changed2 schema fields changedJun 22, 2026

changedOutput schema / properties / alerts / items / properties / validFrom / description

Previous value: -"Validity start parsed from the message body, null if not found."New value: +"Validity-window start as ISO 8601 UTC, parsed from the message body (\"Valid From\" or \"Begin Time\"); null when the product carries no start line."

changedOutput schema / properties / alerts / items / properties / validTo / description

Previous value: -"Validity end parsed from the message body, null if not found."New value: +"Validity-window end as ISO 8601 UTC, parsed from the message body (\"Valid To\", \"Now Valid Until\", or \"End Time\"); null when the product carries no end line."

First observedJun 7, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it explains that the SWPC feed retains all historical records with no built-in expiry, and that max_age_hours controls the lookback window, which could surprise users expecting default feed expiration. It also specifies the effect of active_only=false.

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?

The description is a single, tight paragraph of three sentences. It is front-loaded with the core purpose, then adds parameter behavior without any filler or repetition of schema information. Every sentence contributes a distinct piece of information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (not shown but implied by 'has output schema: true'), the description does not need to enumerate return fields. It covers parameter defaults, edge cases (historical retention, inclusion of expired notices), and the tool's scope. There are no missing details that would prevent correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

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

Both parameters already have detailed schema descriptions covering defaults and filtering behavior, so the baseline is 3. The description adds extra meaning by noting that the feed keeps all historical records and that max_age_hours prevents returning weeks of historical notices as 'active'—a nuance not present in the schema, which only states a maximum and minimum.

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 clearly states a specific verb and resource: returns active SWPC alerts, watches, and warnings, parsed into structured records with explicit fields (product type, NOAA scale, issue time, validity window, plain text). It also names the three storm types covered (geomagnetic storms, radio blackouts, radiation storms), which distinguishes it from sibling tools like aurora forecast or solar wind.

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?

The description provides clear context on what the tool returns and how it behaves with active_only=false, and explains the max_age_hours parameter. However, it does not explicitly name any sibling tools or state when not to use this tool, so there are no explicit exclusions or alternatives mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All noaa-spaceweather-mcp-server tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool targets a distinct aspect of space weather: alerts, aurora forecast, conditions snapshot, Kp index, solar activity, and solar wind. No two tools serve the same purpose, and the descriptions clearly delineate when to use each (e.g., conditions for a quick overview versus Kp for time series detail).

Naming Consistency5/5

All tools follow the exact same pattern: `noaa_spaceweather_get_<resource>`. This is perfectly consistent and predictable, making it easy for an agent to infer tool purpose from the name alone.

Tool Count5/5

With 6 tools, the server covers the major space-weather data categories without being overwhelming. Each tool provides substantial, non-redundant information, and the scope aligns well with what an agent might need for operational space-weather queries.

Completeness5/5

The tool set spans alerts/warnings, current conditions, KP index, solar activity, solar wind, and aurora forecasts – covering the full lifecycle of space-weather monitoring. No obvious missing operations exist; the description even cross-references tools to guide exploration (e.g., conditions leads to solar wind, aurora, or alerts).

Get Space Weather Alerts

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources