AetherLink SDR MCP

by N-Erickson

Overview Schema Source Related Servers Discussions Admin

Python

Local

sdr_set_frequency

Set an SDR's center frequency in Hz to tune RTL-SDR or HackRF hardware for signal analysis and protocol decoding.

Instructions

Set SDR center frequency in Hz

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": {
      "frequency": "<frequency>"
    },
    "name": "sdr_set_frequency"
  }
}

Input Schema

Name	Required	Description	Default
`frequency`	Yes	Frequency in Hz (e.g., 1090000000 for 1090 MHz)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says nothing about whether the change applies immediately, whether it may fail or be clamped for out-of-range values, what happens to dependent settings (sample rate, active decoders), or what errors are returned.

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 compact sentence with no filler and the key unit front-loaded. It is efficient, though the brevity contributes to the missing guidance elsewhere.

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?

For a one-parameter tuning tool with no output schema, the essentials are nearly covered, but without annotations the description should at least mention device-connection prerequisites and how invalid frequencies are handled. It is minimally adequate rather than complete.

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 coverage is 100%, and the schema already documents the single parameter with a unit and an example (1090000000 for 1090 MHz). The description's "in Hz" restates the schema and adds no range or constraint information beyond it, so 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?

States a specific verb and resource ("Set SDR center frequency") with the unit, which distinguishes it from siblings like sdr_set_sample_rate and sdr_set_gain. It does not explicitly name those siblings or clarify selection, but the resource is unambiguous.

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 guidance on when to use this versus sdr_set_sample_rate/sdr_set_gain, and no stated prerequisites such as needing sdr_connect first. The agent must infer usage entirely from the name.

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