Skip to main content
Glama

Space weather and Kp

get_space_weather
Read-onlyIdempotent

Answers: what is the Kp index now and over the next 3 days, is a geomagnetic storm expected, and will GPS be affected by the user's Kp threshold. Uses the Kp source the user's app uses, and labels every value with its source. Anything the plan, region or data sources don't include is listed under "unavailable" with a reason (plan, region, source, setting).

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

Input Schema

NameRequiredDescriptionDefault
placeNoA favorite location's name, a place name, "lat, lon" coordinates, or "here". Times are then local there.
localeNoBCP 47 language tag for labels.

Output Schema

NameRequiredDescriptionDefault
gpsNo
linkNo
noteNo
kp_nowNo
sourceNoSource: UAV Forecast
statusYesok or subscription_required; others may appear.
messageNo
forecastNo
timezoneNo
kp_sourceNouavforecast or noaa.
storm_watchNo
unavailableNo
noaa_forecastNo

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 this a read-only, idempotent, non-destructive closed-world read, so the safety profile is covered. The description adds genuinely new behavior: every value is labeled with its source, and anything excluded by plan, region, source, or setting is surfaced under 'unavailable' with a reason. That partial-result contract is exactly the kind of context annotations cannot express.

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 opening 'Answers:' frame front-loads the concrete questions, followed by two short sentences on sourcing and the 'unavailable' contract. Every sentence carries information, with no filler. Slightly dense phrasing ('the Kp source the user's app uses') but structurally sound.

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?

An output schema exists, so return-value detail is not required, and the description still usefully previews the 'unavailable' field. For a two-optional-parameter read tool with full annotation coverage, this is essentially complete. Only the lack of sibling routing guidance keeps it from the top.

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% and both parameters (place, locale) are documented in the schema, so baseline is 3. The description does not elaborate on place formats or locale behavior beyond the schema. It adds only indirect context via the plan/region/source caveats that explain why some locations may come back unavailable.

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 states concretely what the tool answers: the current Kp index, the 3-day outlook, whether a geomagnetic storm is expected, and GPS impact against the user's Kp threshold. That is a specific resource and scope an agent can match to a space-weather question. It never names or contrasts a sibling such as get_hourly_forecast, so the reader must infer the boundary between space weather and ordinary forecast data.

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 the question list (ask this when the user wants Kp or storm/GPS impact), and 'Uses the Kp source the user's app uses' signals personalization. There is no explicit when-not guidance and no mention of which sibling to call for plain weather or travel decisions. The agent has to derive the routing itself.

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.

Resources