Skip to main content
Glama
Sign In
io.github.qso-graph/ionis-mcp

io.github.qso-graph/ionis-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Current Conditions

current_conditions
Read-onlyIdempotent

Fetches real-time solar flux, Kp index, solar wind, and NOAA alerts, then generates an HF band outlook to help operators choose bands or plan POTA/SOTA activations.

Instructions

Live space weather and band conditions — like a morning propagation forecast.

Fetches real-time solar flux (SFI), Kp index, solar wind data, and active alerts from NOAA SWPC. Generates an operator-friendly band outlook based on current conditions and historical propagation patterns.

Perfect for: "What bands should I use today?" or "Is it worth setting up for POTA/SOTA on 10m?"

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

Input Schema

NameRequiredDescriptionDefault
qth_gridNoYour 4-char Maidenhead grid (e.g., "DN13") for solar elevation context. Optional but recommended.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.9

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful context beyond that by identifying NOAA SWPC as the data source and explaining that it generates a derived band outlook from current conditions and historical propagation patterns.

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 description is short and front-loaded, with the core live space-weather/band-conditions purpose stated immediately. The morning-forecast analogy and example questions are useful, though slightly informal rather than strictly operational.

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 rich annotations, an output schema, and a single optional parameter documented at 100% coverage, the description supplies enough context for an agent to select and call the tool. Minor gaps remain around source availability, latency, or explicit sibling comparisons, but the output schema handles return-value documentation.

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 only one optional parameter, and the schema description coverage is 100%, so the schema already explains qth_grid as a 4-character Maidenhead grid used for solar elevation context. The description does not mention the parameter or add meaning beyond the schema, making 3 the appropriate baseline.

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 uses specific verbs and resources: it fetches real-time SFI, Kp index, solar wind data, and alerts, then generates an operator-friendly band outlook. It is clear what the tool does, but it does not explicitly distinguish itself from related siblings such as band_openings, band_summary, or solar_history.

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?

The 'Perfect for' examples give clear use cases, such as deciding which bands to use today or whether POTA/SOTA on 10m is worthwhile. It does not state when not to use it or name alternative tools, so it falls short of explicit routing guidance.

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

Deploy Server

Other Tools