Skip to main content
Glama

Aurora Forecast and Kp Index MCP

Aurora right now

aurora_now
Read-only

Is the aurora visible right now from a place? NOAA's OVATION nowcast probability overhead and on the poleward horizon (next 30 to 90 minutes), the current Kp index, whether it is dark and the current cloud cover.

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_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYesPlace like "Fairbanks, Alaska", "Tromso", "Reykjavik", "Minneapolis", or "lat,lon".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: a live NOAA OVATION nowcast source, a 30-90 minute validity window, and the specific quantities combined into the answer. With no output schema, this prose is the only place an agent learns what the result contains.

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?

A single front-loaded sentence that leads with the user-facing question before the technical detail, with no filler. It is dense and slightly run-on, packing data sources, horizon semantics, and the time window into one clause chain, but each element earns its place.

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 simple one-parameter read tool with no output schema, the description is nearly sufficient: it enumerates the returned signals and their freshness window. Remaining gaps are minor, such as output formatting, units for probability or Kp, and behavior when the location string cannot be resolved.

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?

There is a single parameter with 100% schema description coverage, including concrete place-name and 'lat,lon' examples, so the schema carries the semantics. The description adds only the general notion of 'a place' and does not clarify geocoding behavior, ambiguity handling, or coordinate format beyond what the schema already states.

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?

Opens with a specific question the tool answers ('Is the aurora visible right now from a place?') and names the concrete data products: OVATION nowcast probability overhead and on the poleward horizon, current Kp index, darkness, and cloud cover. The 'right now' framing implicitly distinguishes it from the 'tonight' forecast sibling, but no sibling is named explicitly.

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?

The '(next 30 to 90 minutes)' window and 'right now' phrasing imply this is for immediate conditions rather than advance planning, which nudges an agent toward the forecast siblings for future dates. However, no alternative tool is named and there is no explicit when-not guidance or prerequisite statement.

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.