Tanod MCP server

skypeek: aurora chance at a location

aurora_forecast

Read-onlyIdempotent

Check the chance of visible aurora overhead at a given latitude and longitude for the next 30-90 minutes, including Kp index and darkness conditions.

Instructions

skypeek: Aurora forecast: the chance of visible aurora at a location in the next 30-90 minutes. For Kp and solar wind use get_space_weather. Returns the chance (0 to 100 percent) of visible aurora overhead at a point from NOAA SWPC's OVATION model for the next 30-90 minutes, with the current Kp, the Sun's altitude and whether it is dark enough. Data: NOAA Space Weather Prediction Center (public domain), a derived copy, not an official NOAA product; no endorsement by NOAA or the National Weather Service is implied. The model assumes a dark, clear sky: cloud, moonlight and light pollution are not modelled. Cached up to 10 minutes. An upstream outage is a 503 upstream_unavailable (not charged). Typically under 1 s cached, a few seconds on a refresh. Price: USD 0.001. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/space-weather-kp-index-aurora-api.html

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lat`	Yes	Latitude in degrees (-90 to 90).
`lon`	Yes	Longitude in degrees (-180 to 180).

Output Schema

TableJSON Schema

Name	Required	Description
`kp`	No
`lat`	No
`lon`	No
`note`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`stale`	No
`cached`	No
`source`	No
`grid_point`	No
`likelihood`	No
`attribution`	No
`dark_enough`	No
`cache_seconds`	No
`probability_pct`	No
`sun_altitude_deg`	No
`model_forecast_time`	No
`model_observation_time`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world. The description adds substantial behavioral context: return semantics, 10-minute cache, 5 free calls per IP per day, USD 0.001 price, upstream outage as 503 upstream_unavailable (not charged), typical latency, NOAA SWPC provenance, and model limitations.

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?

Front-loaded with the purpose and the get_space_weather alternative in the first two sentences. Later sentences are dense and mostly useful (returns, caveats, caching, pricing, docs), though the NOAA endorsement disclaimer is less critical for tool selection. Slightly long but not repetitive.

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?

An output schema exists, yet the description also explains return fields. It covers parameters, return semantics, model caveats, error behavior, pricing, caching, and documentation, leaving nothing needed for correct invocation missing.

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 description coverage is 100% and both lat and lon are documented with ranges. The description adds only that the forecast is for a location/point, which does not go beyond the schema's syntax or constraints, so the baseline of 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?

States a specific verb (forecast) and resource (chance of visible aurora at a location in the next 30-90 minutes). Directly distinguishes itself from the sibling get_space_weather by routing Kp and solar wind queries there.

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

Usage Guidelines5/5

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

Explicitly names get_space_weather as the alternative for Kp and solar wind. The caveat that the model assumes a dark, clear sky and ignores cloud, moonlight, and light pollution tells the agent when results may be misleading.

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

Deploy Server