AetherLink SDR MCP

Overview Schema Source Related Servers Discussions Admin

sdr_list_devices

Lists attached RTL-SDR and HackRF devices with index, name, and serial without opening them, so you can identify available radios before configuring or starting signal analysis.

Instructions

List attached RTL-SDR and HackRF devices (index, name, serial) without opening them

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sdr_list_devices"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`devices`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key trait: the call does not open or claim the device, so it has no side effects on an in-use radio. It omits edge behavior (what is returned when nothing is attached) and any permission/hardware-state prerequisites.

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?

A single sentence with the action, the hardware scope, the returned fields, and the non-opening guarantee all front-loaded. Nothing is redundant.

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?

For a zero-parameter list call with an output schema, the description covers what the agent needs to decide to call it. Minor gap: it does not state behavior when no devices are present, and does not distinguish itself from ism_get_devices.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to add beyond the schema; the baseline of 4 applies. The parenthetical field list usefully previews the output shape rather than describing inputs.

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?

States a specific verb and resource ('List attached RTL-SDR and HackRF devices') and enumerates the returned fields (index, name, serial). The qualifier 'without opening them' immediately separates it from sdr_connect and the set_* siblings.

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?

'without opening them' implies this is the enumeration step before sdr_connect, so usage context is inferable. However, no alternative is named explicitly, and the sibling ism_get_devices (also a device lister) is not differentiated from, leaving a real ambiguity for the agent.

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