Skip to main content
Glama

Aurora Forecast and Kp Index MCP

Northern lights forecast tonight

aurora_tonight
Read-only

Can I see the northern lights (or southern lights) tonight from a place? Hour by hour through the dark hours: NOAA's predicted Kp index, whether the auroral oval reaches overhead or the horizon there, cloud cover, and a good/possible/unlikely verdict with the best window. Up to 3 nights.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "location": "<location>"
    },
    "name": "aurora_tonight"
  }
}

Input Schema

NameRequiredDescriptionDefault
nightsNoNights ahead, 1 to 3. Default 1.
locationYesPlace like "Fairbanks, Alaska", "Tromso", "Reykjavik", "Minneapolis", or "lat,lon".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and non-destructive behavior, so the safety profile is covered. The description adds meaningful context beyond that: the data sources (NOAA Kp, auroral oval, cloud cover), the verdict categories, and the 3-night cap, which helps the agent interpret results even without an output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The framing question is front-loaded and the following clause packs the return contents efficiently. It is dense but every element (Kp, oval, clouds, verdict, window, night cap) earns its place; only the parenthetical '(or southern lights)' is slightly extraneous.

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?

With no output schema, the description carries the burden of explaining return values and does so well by listing the forecast components and verdict scale. It is nearly complete for a two-parameter read-only tool, with only minor gaps such as whether results are cached or how far ahead data is reliable.

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%, with both parameters fully documented including examples and the 1-3 range. The description only restates the 'up to 3 nights' limit and adds no format or syntax detail beyond the schema, so baseline 3 applies.

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 states a specific question the tool answers (aurora visibility tonight from a place) and enumerates exactly what it returns: hourly Kp index, oval reach, cloud cover, verdict, and best window. This scope is distinguishable from a bare Kp forecast or a current-conditions sibling without opening the schema.

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 implied by 'tonight' and 'Up to 3 nights,' which tells the agent the time horizon, but there is no explicit when-to-use/when-not guidance and no sibling is named as an alternative for, say, comparing multiple locations or checking raw Kp.

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.