AetherLink SDR MCP

Overview Schema Source Related Servers Discussions Admin

spectrum_scan

Scan a frequency range for signals across up to 2000 steps to locate transmissions and identify active channels for SDR signal analysis.

Instructions

Scan a frequency range for signals (at most 2000 steps)

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": {
      "start_freq": "<start_freq>",
      "stop_freq": "<stop_freq>"
    },
    "name": "spectrum_scan"
  }
}

Input Schema

Name	Required	Description
`step`	No	Step size in Hz (must be > 0)
`stop_freq`	Yes	Stop frequency in Hz
`dwell_time`	No	Dwell time per frequency in seconds (0.01-5)
`start_freq`	Yes	Start frequency in Hz

Output Schema

Name	Required	Description	Default
`results`	No
`summary`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 7, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuine behavioral trait not present in the schema: a 2000-step ceiling. However it says nothing about blocking/synchronous behavior, expected sweep duration (which follows from step count and dwell_time), or what happens when the cap is exceeded.

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?

A single short sentence with the key constraint in a parenthetical; nothing is wasted and the purpose leads. It is efficient, though the terse structure leaves no room for the routing and prerequisite information an agent needs.

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

Completeness2/5

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

For a four-parameter hardware sweep with no annotations and a close sibling (spectrum_analyze), the description omits device/session prerequisites, call duration and blocking semantics, and behavior at the step limit. The output schema covers return values, so that omission is acceptable, but the invocation-side gaps remain.

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 the baseline is 3. The description adds the 2000-step cap, which implicitly constrains the start_freq/stop_freq/step combination, but it never states the relationship ((stop-start)/step) so the agent must derive the trade-off itself.

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?

Names a specific verb and resource ('Scan a frequency range for signals') plus a hard invocation limit (2000 steps), so the agent knows exactly what the tool does. It does not distinguish itself from the sibling spectrum_analyze, which is the obvious confusion risk.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance at all: nothing says how this differs from spectrum_analyze, ism_start_scanning, or pager_find_frequencies, and no prerequisites (e.g. an active sdr_connect session) are stated. The agent must infer selection purely from the tool name.

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