Skip to main content
Glama

Aurora Forecast and Kp Index MCP

Space weather alerts

space_weather_alerts
Read-only

Recent NOAA SWPC space weather alerts, watches and warnings: geomagnetic storm watches (aurora outlook), Kp warnings, solar radiation and radio blackout alerts, newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "space_weather_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoLook back this many hours. Default 48.
geomagnetic_onlyNoOnly geomagnetic (Kp, storm watch) messages. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds value by identifying the upstream source (NOAA SWPC) and the result ordering ("newest first"), which explains the non-idempotent hint. It leaves out volume expectations, empty-result behavior, and whether duplicate/updated alerts appear, so it is not fully exhaustive.

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?

A single front-loaded sentence with the resource first, the covered message types second, and the ordering convention last. Every clause carries information; nothing is repeated from the title or schema.

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 two-optional-parameter read tool with rich annotations, the description supplies the source, the content taxonomy, and the ordering an agent needs to decide and interpret results. With no output schema present, it could say slightly more about the shape of a returned alert, but the essential decision information is there.

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 coverage is 100%, so both parameters and their defaults (48h, false) are already documented. The description hints at the geomagnetic filter by calling out "geomagnetic storm watches (aurora outlook)" but adds no format or interaction detail beyond the schema, making the baseline 3 appropriate.

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 names a specific verb+resource ("Recent NOAA SWPC space weather alerts, watches and warnings") and enumerates the message families covered (geomagnetic storm watches/aurora outlook, Kp warnings, solar radiation, radio blackout). That content set clearly separates it from the sibling aurora_* and kp_forecast tools without naming them, so it stops just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: "Recent" plus "newest first" signals a live/recent-feed tool. There is no explicit when-to-use versus the aurora_now/kp_forecast siblings, no stated exclusions, and no note on when an agent should prefer a forecast tool instead.

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.