Skip to main content
Glama

noaa-spaceweather-mcp-server

by io.github.cyanheads

Get Solar Activity

noaa_spaceweather_get_solar_activity
Read-onlyIdempotent

Solar flare and radiation storm picture: recent GOES X-ray flux with flare-class labels (A/B/C/M/X), 3-day flare-class probabilities (C/M/X), active solar regions with per-region flare probabilities, and GOES integral proton flux at ≥10 MeV with NOAA S-scale. For operators tracking HF radio blackout (R-scale, driven by X-ray) and radiation storm risk (S-scale, driven by protons). Active region data helps identify which region is driving current activity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_regionsNoInclude active solar region details (default true). Set false to skip region data and reduce response size.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
sScaleNoCurrent NOAA S-scale for solar radiation storms (0–5), derived from latest proton flux.
fetchedAtNoISO 8601 timestamp of when this data was fetched.
latestXrayNoMost recent GOES X-ray flux reading, null if unavailable.
recentXrayNoGOES X-ray flux readings from the past hour, oldest first.
sScaleTextNoPlain-language S-scale description, e.g. "S2 moderate radiation storm".
latestProtonNoMost recent ≥10 MeV proton flux reading, null if unavailable.
activeRegionsNoCurrently active solar regions with per-region flare probabilities. Empty when include_regions=false or no regions are active.
probabilitiesNo3-day flare probability forecasts.

Schema Changelog

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

  1. 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": [
+      "latestXray",
+      "recentXray",
+      "probabilities",
+      "latestProton",
+      "sScale",
+      "sScaleText",
+      "activeRegions",
+      "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: -[
-  "latestXray",
-  "recentXray",
-  "probabilities",
-  "latestProton",
-  "sScale",
-  "sScaleText",
-  "activeRegions",
-  "fetchedAt"
-]
  2. Changed9 schema fields changed
    • changedOutput schema / properties / probabilities / items / properties / cClass1Day / description
      Previous value: -"Total probability of a C-class flare for this day (%)."New value: +"Total probability of a C-class flare for this date (%)."
    • addedOutput schema / properties / probabilities / items / properties / cClassProbability
      Added value: +{
+  "description": "Total probability of a C-class flare for this date (%). Date-neutral alias of cClass1Day.",
+  "type": "number"
+}
    • changedOutput schema / properties / probabilities / items / properties / mClass1Day / description
      Previous value: -"Total probability of an M-class flare for this day (%)."New value: +"Total probability of an M-class flare for this date (%)."
    • addedOutput schema / properties / probabilities / items / properties / mClassProbability
      Added value: +{
+  "description": "Total probability of an M-class flare for this date (%). Date-neutral alias of mClass1Day.",
+  "type": "number"
+}
    • addedOutput schema / properties / probabilities / items / properties / protonEventProbability
      Added value: +{
+  "description": "Probability of a ≥10 MeV proton event for this date (%). Date-neutral alias of protons1Day.",
+  "type": "number"
+}
    • changedOutput schema / properties / probabilities / items / properties / protons1Day / description
      Previous value: -"Probability of ≥10 MeV proton event for this day (%)."New value: +"Probability of a ≥10 MeV proton event for this date (%)."
    • changedOutput schema / properties / probabilities / items / properties / xClass1Day / description
      Previous value: -"Total probability of an X-class flare for this day (%)."New value: +"Total probability of an X-class flare for this date (%)."
    • addedOutput schema / properties / probabilities / items / properties / xClassProbability
      Added value: +{
+  "description": "Total probability of an X-class flare for this date (%). Date-neutral alias of xClass1Day.",
+  "type": "number"
+}
    • changedOutput schema / properties / probabilities / items / required
      Previous value: -[
-  "date",
-  "cClass1Day",
-  "mClass1Day",
-  "xClass1Day",
-  "protons1Day"
-]New value: +[
+  "date",
+  "cClass1Day",
+  "cClassProbability",
+  "mClass1Day",
+  "mClassProbability",
+  "xClass1Day",
+  "xClassProbability",
+  "protons1Day",
+  "protonEventProbability"
+]
  3. Changed1 schema field changed
    • changedOutput schema / properties / latestProton / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "description": "One GOES integral proton flux reading with S-scale.",
-    "properties": {
-      "energy": {
-        "description": "Energy channel, e.g. \">=10 MeV\".",
-        "type": "string"
-      },
-      "fluxPfu": {
-        "description": "Integral proton flux in particle flux units (pfu) at ≥10 MeV.",
-        "type": "number"
-      },
-      "sScale": {
-        "description": "NOAA S-scale level (0–5) for this flux reading.",
-        "type": "number"
-      },
-      "timeTag": {
-        "description": "ISO 8601 measurement time tag.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "timeTag",
-      "fluxPfu",
-      "sScale",
-      "energy"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "description": "One GOES integral proton flux reading with S-scale.",
+    "properties": {
+      "energy": {
+        "description": "Energy channel, e.g. \">=10 MeV\".",
+        "type": "string"
+      },
+      "fluxPfu": {
+        "description": "Integral proton flux in particle flux units (pfu) at ≥10 MeV, rounded to 3 significant figures.",
+        "type": "number"
+      },
+      "sScale": {
+        "description": "NOAA S-scale level (0–5) for this flux reading.",
+        "type": "number"
+      },
+      "timeTag": {
+        "description": "ISO 8601 measurement time tag.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "timeTag",
+      "fluxPfu",
+      "sScale",
+      "energy"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already provide readOnlyHint and idempotentHint, so the description does not need to restate safety. It adds value by describing the data composition and explaining that 'Active region data helps identify which region is driving current activity,' giving behavioral context beyond the annotation metadata. It does not contradict annotations.

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 compact and front-loaded with the core concept ('Solar flare and radiation storm picture:'), then enumerates specific data points and finishes with the operational significance. There is no redundancy; every sentence contributes to understanding the tool's functionality and relevance.

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 tool is read-only with one optional parameter and an output schema present, the description effectively covers what data is returned, the purpose, and the use case. It explains the meaning of the data (R-scale, S-scale, active regions) sufficiently for an agent to decide when to invoke it. Nothing essential is missing.

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?

The input schema has 100% description coverage, documenting the include_regions parameter with its default and purpose. The description mentions active region data but does not directly explain the parameter, so it adds minimal extra meaning beyond what the schema already provides. Baseline of 3 is appropriate given full schema coverage.

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?

The description clearly states the tool provides a 'Solar flare and radiation storm picture' with specific data elements (GOES X-ray flux, flare-class probabilities, active regions, proton flux). It identifies the resource and content uniquely, but does not explicitly distinguish it from sibling tools like get_alerts or get_conditions, though the described data is clearly distinct.

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 gives explicit context for when to use it: 'For operators tracking HF radio blackout (R-scale, driven by X-ray) and radiation storm risk (S-scale, driven by protons).' This clarifies the intended use case and target audience, though it does not mention alternatives or when not to use other tools.

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 toolsInspect
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).

Resources