Skip to main content
Glama
Sign In
solar-mcp

solar-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Solar Band Outlook

solar_band_outlook
Read-onlyIdempotent

Get an HF band-by-band propagation outlook derived from current SFI and Kp values, so you can choose which band to operate now.

Instructions

Get HF band-by-band propagation outlook based on current conditions.

Derives a propagation assessment for each HF band (160m through 6m) from the current SFI and Kp values. Useful for deciding which band to operate on right now.

Each band is rated " — ", the status one of five words defined in BAND-OUTLOOK.md: Excellent (wide open, strong long-lasting DX), Good (regular DX openings in the band's usual hours), Fair (short, patchy or weak openings; DX possible, not dependable), Poor (likely closed for DX, or degraded by absorption and noise), Sporadic (not graded from the indices: 6m opens by sporadic-E, and by F2 at high solar flux). The thresholds are rules of thumb on SFI and Kp, not a propagation model.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare it as a safe, idempotent, open-world read; the description goes beyond that by disclosing the derivation source (current SFI and Kp), the fact that thresholds are rules of thumb rather than a propagation model, and the special-cased 6m Sporadic rating that is not graded from indices. That is exactly the kind of interpretive caveat an agent needs to trust and frame the output.

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 purpose and scope, then the rating vocabulary, then the caveat. The five-status enumeration is somewhat long and partially overlaps the available output schema, but it earns its place as interpretive guidance rather than raw format description.

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?

For a zero-parameter tool with an output schema, the description supplies the missing semantic layer: what the status words mean, how they are derived, and their limits. Nothing an agent needs to select or interpret this tool is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly notes the implicit inputs (current SFI and Kp) are read from ambient conditions rather than passed in.

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?

Specific verb + resource: derives an HF band-by-band propagation assessment from current SFI/Kp, which cleanly separates it from the raw-data siblings (solar_conditions, solar_forecast, solar_wind). It also states scope (160m through 6m) and the consumer decision it supports.

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?

"Useful for deciding which band to operate on right now" gives a clear usage context and implies the input dependency (current SFI and Kp). It does not explicitly route to siblings (e.g. use solar_conditions for the raw numbers), so it falls short of full when/when-not 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