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

Dark Hour Analysis

dark_hour_analysis
Read-onlyIdempotent

Classifies HF propagation paths by solar elevation at both endpoints for a band and UTC hour, flagging both-dark and cross-terminator paths to identify anomalous conditions.

Instructions

Classify propagation paths by solar geometry — both-day, cross-terminator, or both-dark.

For a given band and hour, retrieves paths and classifies each by the solar elevation at both endpoints. Useful for identifying physically anomalous paths (e.g., 10m both-dark propagation).

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": {
      "band": "<band>",
      "hour": "<hour>"
    },
    "name": "dark_hour_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandYesADIF band ID (102-111)
hourYesUTC hour (0-23)
monthNoMonth (1-12) for solar geometry (default: all months aggregated)
sourceNoDataset source (default: "pskr" for most recent data)pskr
min_spotsNoMinimum spot count filter (default: 10)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.9

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds the classification categories and endpoint solar-elevation basis, but does not provide further behavioral context such as how min_spots or source affect results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with the core classification purpose and then briefly explains the retrieval/classification behavior and use case. It is appropriately sized with no redundant or filler sentences.

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?

Given the existing output schema and complete parameter descriptions, the definition provides enough context to call the tool correctly. The main remaining gap is routing guidance relative to sibling tools like path_analysis or solar_correlation.

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%, so all five parameters are already documented in the schema. The description reinforces that band and hour drive the analysis, but adds no extra meaning for month, source, or min_spots beyond what the schema provides.

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 a specific verb and resource: classify propagation paths by solar geometry, naming the three output categories. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as path_analysis or solar_correlation.

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?

It gives a clear usage context — for a given band and hour, and useful for identifying physically anomalous paths like 10m both-dark propagation. However, it does not state when not to use this tool or name alternatives for similar path/solar analysis tasks.

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