Skip to main content
Glama
Sign In
AetherLink SDR MCP

AetherLink SDR MCP

by N-Erickson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sdr_disconnect

Stops all active SDR operations and disconnects from the connected radio hardware, ending the session and releasing the device.

Instructions

Stop all activity and disconnect from SDR hardware

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_disconnect"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations at all, the description must carry the whole behavioral burden. 'Stop all activity' usefully discloses the blast radius (it terminates streaming/decoding, not just one task) and 'disconnect from hardware' indicates the device is released. It does not say whether the call errors when already disconnected, whether settings are preserved, or what the response contains.

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 short sentence with the action and scope front-loaded and no filler. Nothing could be removed without losing meaning.

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 teardown tool with no output schema, the definition covers the essential behavior. The main missing piece is lifecycle context — that subsequent SDR calls will need sdr_connect again and that it is safe/idempotent to call when already stopped.

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 nothing for the description to disambiguate; baseline 4 applies. The description correctly avoids inventing argument details for a no-arg call.

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 ('Stop') plus a resource ('SDR hardware') and adds scope with 'all activity and disconnect', which makes the effect concrete. It is clearly the inverse of the sibling sdr_connect, though it never names that or any other sibling explicitly.

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?

The intent is implied: call this to tear down SDR activity and release the device, typically at the end of a session. There is no explicit guidance on prerequisites (must a connection exist first?), no mention of what other SDR tools require reconnecting afterward, and no stated alternatives or exclusions.

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