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

Path Analysis

path_analysis
Read-onlyIdempotent

Analyze HF propagation between two Maidenhead grids across all bands and hours, ranking band/hour reliability with distance, azimuth, seasonal trends, solar geometry, and observation counts.

Instructions

Complete analysis of a propagation path across all bands and hours.

Provides distance/azimuth, best band/hour combinations ranked by reliability, seasonal patterns, solar geometry, and total observation counts from all available data sources.

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": {
      "tx_grid": "<tx_grid>",
      "rx_grid": "<rx_grid>"
    },
    "name": "path_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoDataset source or "all"all
rx_gridYesReceiver 4-char Maidenhead grid
tx_gridYesTransmitter 4-char Maidenhead grid

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.9

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully carried there. The description adds that results derive from 'all available data sources' and enumerates the analytical dimensions, which is modestly useful context beyond the annotations but doesn't discuss cost, data coverage limits, or missing-data behavior.

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?

Two tight sentences, front-loaded with the scope ('across all bands and hours') before the output inventory. No filler, though the output enumeration is largely redundant given a declared output schema.

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 the description need not detail return values, and it covers scope and analytical breadth well. It doesn't address what happens with sparse paths or whether source filtering changes the aggregation, but nothing essential to calling it is 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%, so tx_grid, rx_grid, and source are already documented in the schema. The description adds no parameter-level meaning — it never mentions grids or the source filter — so the baseline 3 applies.

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?

Specific verb+resource: it performs a 'complete analysis of a propagation path' spanning all bands and hours, which distinguishes it from narrower siblings like band_openings or solar_correlation. It stops short of naming any sibling explicitly, so an agent must infer the boundary itself.

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 only implied by the word 'complete' and 'all bands and hours' — suggesting this is the broad aggregate to reach for when you want everything at once. There is no explicit when-to-use, when-not, or named alternative among the eleven siblings.

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