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

Band Summary

band_summary
Read-onlyIdempotent

Generates an overview of an HF band across all sources and hours, summarizing total signatures, spots, grid pairs, SFI range, and distance distribution.

Instructions

Overview of a band across all hours and available sources.

Shows total signatures and spots, hour distribution, top grid pairs, SFI range observed, and distance distribution.

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>"
    },
    "name": "band_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandYesADIF band ID (102-111)
sourceNoDataset source or "all"all

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.9

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful scope context by saying it aggregates across all hours and available sources and lists what the summary contains, but it does not disclose operational details such as data freshness, limitations, or rate behavior.

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 description is two short sentences with the main purpose front-loaded and the included summary outputs listed compactly. Every sentence contributes to understanding the tool's scope.

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 rich annotations, full schema descriptions, and presence of an output schema, the description is largely complete for correct invocation. It could be slightly stronger with explicit routing guidance versus sibling tools, but it covers the core scope and contents.

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 both the required band ID and the source parameter are already documented in the schema. The description does not add format or constraint details beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states that this tool provides an overview of a band across all hours and available sources, and it lists the summary metrics included. It does not explicitly differentiate itself from siblings such as query_signatures or compare_sources, so it is clear but not fully sibling-aware.

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?

There is no explicit when-to-use guidance or named alternative, but the word 'Overview' and the scope 'across all hours and available sources' imply that this is for broad aggregate inspection rather than detailed querying. The usage context is therefore implied rather than stated.

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