Skip to main content
Glama

Noaa Swpc

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Kp Index

kp_index
Read-onlyIdempotent

NOAA planetary K-index — global geomagnetic activity 0–9, the standard aurora/storm indicator (Kp≥5 is a geomagnetic storm). Windows: now (single freshest estimated value) | 1-day (3-hourly observed, feed carries about a week) | 7-day (observed plus 3-day forecast; each row flags which) | 1-minute (1-minute estimated, last ~6 hours). SWPC retired its 30-day archive, so no month-long Kp history is available from this source.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNonow | 1-day (default) | 7-day | 1-minute

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNo
countNo
sourceNo
windowNo
cadenceNo
coverageNo
measurementsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / window / description
      Previous value: -"1-day (default) | 7-day | 30-day | now"New value: +"now | 1-day (default) | 7-day | 1-minute"
    • addedOutput schema / properties
      Added value: +{
+  "cadence": {
+    "type": "string"
+  },
+  "count": {
+    "type": "number"
+  },
+  "coverage": {
+    "properties": {
+      "newest": {
+        "type": "string"
+      },
+      "oldest": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "kind": {
+    "type": "string"
+  },
+  "measurements": {
+    "items": {
+      "properties": {
+        "Kp": {
+          "type": "number"
+        },
+        "a_running": {
+          "type": "number"
+        },
+        "station_count": {
+          "type": "number"
+        },
+        "time_tag": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "source": {
+    "type": "string"
+  },
+  "window": {
+    "type": "string"
+  }
+}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "window": "1-day"
+  },
+  {
+    "window": "7-day"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Planetary K-index data in various time windows",
+  "type": "object"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent, and the description adds detail on data freshness, observed vs forecast mix for the 7-day window, and the estimated nature of 'now' and '1-minute'. It also discloses the SWPC 30-day archive retirement, a meaningful behavioral limitation.

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 dense sentences with no filler; the core definition, window breakdown, and limitation are all front-loaded and prioritized.

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?

For a single-parameter data fetch tool, the description covers data source, all window semantics, and a key limitation. With an output schema present, this is ample context.

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

Parameters5/5

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

The schema defines the one `window` param with allowed values, and the description adds semantics for each value: 'now' is a single freshest estimate, '1-day' is 3-hourly observed, '7-day' includes forecast with flags, '1-minute' is estimated for last ~6 hours. This fully enriches the parameter beyond the enum.

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 the tool returns the NOAA planetary K-index, a 0–9 geomagnetic activity scale, and standard aurora/storm indicator. It distinguishes windows (now, 1-day, 7-day, 1-minute) and notes the Kp≥5 storm threshold, setting it apart 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?

Provides clear context for when to use: it is the standard Kp indicator with specific temporal windows and notes that no 30-day history is available, implicitly guiding against month-long requests. However, it does not explicitly name alternative tools or state 'use this when...' exclusions.

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

All Noaa Swpc toolsInspect
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.

Resources