Skip to main content
Glama

Aurora Forecast and Kp Index MCP

Kp index forecast

kp_forecast
Read-only

NOAA's planetary Kp index forecast for the next three days in 3-hour UTC blocks, with the NOAA G-scale storm level, plus the last 24 hours observed and the daily maximum. Kp 5 or more is a geomagnetic storm and pushes aurora toward mid latitudes.

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": "kp_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this as a read-only, open-world, non-destructive, non-idempotent operation. The description adds useful behavioral context about what is returned, including observed history and daily maxima, but does not discuss update cadence, freshness, or reliability of the forecast. For a simple no-parameter read tool, this is solid but not 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?

Two sentences, front-loaded with the core purpose and time range, followed by a practical interpretation note. Every phrase adds information about content or meaning; there is no filler.

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?

With no input parameters, no output schema, and only annotation-level safety metadata, the description carries the full burden of explaining what the tool returns. It does so clearly by naming the forecast horizon, block size, storm scale, observed history, and daily maximum, leaving no major ambiguity for an agent deciding whether to call it.

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?

The tool has zero parameters, which establishes a baseline of 4. There are no parameter semantics to clarify, and the description appropriately focuses on output content instead.

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 gives a specific resource (NOAA planetary Kp index forecast), a precise scope (next three days in 3-hour UTC blocks), and the additional content returned (G-scale storm level, last 24 hours observed, daily maximum). This is specific enough that an agent can distinguish it from sibling aurora tools that answer current or location-specific conditions.

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?

Usage is clearly implied by the time horizon and the note that Kp 5+ indicates a geomagnetic storm and pushes aurora toward mid latitudes, which tells the agent when this forecast is relevant. It does not explicitly name alternatives or state when not to use it, so it falls short of full when/when-not guidance.

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.