Skip to main content
Glama

wspr_longest_paths

Detect open bands by fetching the longest WSPR paths within a selected time window and minimum distance.

Instructions

Get the longest WSPR paths in the given time window.

WSPR's precise timing and low power make it the gold standard for detecting marginal propagation. Long paths here prove the band is open.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bandNoFilter by band (e.g., 20m, 10m). Empty for all bands.
hoursNoTime window in hours (1-72, default 24).
limitNoMaximum paths to return (1-50, default 20).
min_distanceNoMinimum distance in km (e.g., 15000 for near-antipodal).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided; description carries full burden. Only states the tool is for reading longest paths but omits any behavioral traits like cost, caching, or side effects. Minimal transparency beyond purpose.

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?

Two concise sentences. First directly states purpose, second adds relevant context about WSPR's significance. No wasted words or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has 4 optional parameters, output schema exists. Description covers purpose but lacks behavioral context (e.g., whether the tool is expensive). Adequate but not comprehensive for a complex radio propagation tool.

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 covers all 4 parameters with descriptions (100% coverage). Description adds no extra semantic meaning; it only mentions 'time window' which is already in schema. Baseline 3 applies.

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?

Description clearly states 'Get the longest WSPR paths in the given time window.' Verb 'get' and resource 'longest paths' are specific. Distinguishes from siblings like wspr_spots or wspr_propagation by focusing on longest paths.

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?

Implies usage for detecting band openness via long paths ('Long paths here prove the band is open'), but no explicit comparison to sibling tools or when-not-to-use. Agent must infer context from WSPR significance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/qso-graph/wspr-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server