Skip to main content
Glama
Sign In
AetherLink SDR MCP

AetherLink SDR MCP

by N-Erickson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

recording_start

Start recording raw IQ samples (complex float32) to a file to enable offline signal analysis and protocol decoding. Add an optional description to label the capture.

Instructions

Start recording raw IQ samples (complex float32) to a file

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": "recording_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionNoRecording description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure and only states the output data form. It says nothing about where the file is written, how it is named, whether it overwrites existing files, whether a device must be connected or configured first, or whether the recording runs until stopped.

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 tight sentence with the key detail (raw IQ, complex float32) front-loaded and no wasted words. It is appropriately sized for what it actually says, though brevity here reflects omission rather than efficiency.

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 stateful capture tool with no annotations and no output schema, the definition leaves out essential facts: file destination and naming, prerequisites (connected and tuned SDR), and how capture terminates. An agent could invoke it but cannot predict side effects.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already conveys its meaning. The description adds no extra detail about how the description string is used, 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?

Description gives a specific verb and resource ("Start recording") and pins down the data format (raw IQ samples, complex float32), which distinguishes it from the sibling audio_record_start. It stops short of noting any scope limits relative to recording_stop or other SDR tools.

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 or when-not-to-use guidance, no mention that it pairs with recording_stop to end the capture, and no prerequisite such as an active sdr_connect session. The agent must infer all invocation context from sibling names.

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