Static source inference · medium confidence · detected: Logging
Deprecated protocol patterns detected
Summary
AetherLink SDR MCP has 23 tools with generally good naming conventions (verb_noun patterns like sdr_connect, aviation_track_aircraft, spectrum_analyze). However, the server exhibits significant gaps in parameter descriptions and output schema documentation. Tool descriptions are adequate but generic (averaging ~100-150 chars, below the 194-char production baseline). Critical issues: (1) NO parameter descriptions are visible in the source code, ALL 23 tools register schemas without describing what each parameter controls, violating the pattern:tool-description pattern. (2) Output schemas are completely undocumented, the server provides no type information about what these tools return, making it impossible for LLMs to plan downstream calls or validate responses. (3) Error handling is minimal, SDRError is defined but no recovery guidance or actionable error messages are visible. (4) Some parameters lack enums or constraints despite accepting only specific values (e.g., demod_mode should be enum but is free-form). The server would be unusable by a production agent without significant documentation expansion.
CRITICAL: All 23 tools have input schemas with properties but NO parameter descriptions. Schemas define types (string, number, integer) and enums, but the 'description' field for each parameter is missing. LLMs cannot understand what each parameter controls or how to use it.
Add a 'description' field to EVERY parameter in all 23 tools. For example, in sdr_connect, the 'device_type' param needs: 'description': 'Type of SDR hardware to connect to. RTL-SDR is a common USB dongle receiver; HackRF is a software-defined transceiver with transmit capability.'
Document output schemas for all tools, especially getter functions (sdr_get_status, aviation_get_aircraft, etc.). Example: 'Returns an object with fields: connected (boolean), device_name (string), frequency (number in Hz), sample_rate (number), gain (number or 'auto'), is_capturing (boolean), active_decoders (array of strings).'
Add 'required' arrays to all parameter sets. E.g., in spectrum_analyze, mark 'duration' as required if it has no default, or add default if optional.
Document binary dependencies in tool descriptions. E.g., aviation_track_aircraft: 'Requires dump1090 to be installed and available in PATH. Call this first to check: sdr_get_status().'
Implement result limits and pagination. Add max_results/limit parameters (default 50, max 200) to aviation_get_aircraft, marine_get_vessels, ism_get_devices, and frequency_scan.
Add recovery guidance to error handling. When sdr_connect fails, return: 'Failed to connect to device_index=0: libusb error. Try (1) reconnecting the device, (2) checking device_index with a lower value, or (3) calling list_devices first if available.'
Add minimum/maximum constraints to numeric parameters. E.g., frequency must be within supported range (28 MHz to 1.7 GHz for RTL-SDR); gain must be 0-50 dB. Add these to parameter descriptions.
Spec posture evidence
Inferred effective spec: <=2025-11-25.
Relies on Logging (deprecated) - log to stderr or use OpenTelemetry
Start decoding POCSAG pager messages on current frequency
pager_stop_decodingwritesource verified57/100
Stop decoding POCSAG pager messages
satellite_decode_lrptread only50/100
Decode Meteor-M LRPT satellite imagery with SatDump
sdr_connectwritesource verified67/100
Connect to SDR hardware (RTL-SDR or HackRF)
sdr_disconnectwritesource verified57/100
Disconnect from SDR hardware
sdr_get_statusread onlysource verified52/100
Get current SDR status and configuration
sdr_set_frequencywritesource verified62/100
Set SDR center frequency in Hz
sdr_set_gainwritesource verified63/100
Set SDR gain in dB or 'auto'
spectrum_analyzeread onlysource verified65/100
Analyze current spectrum and detect signals
spectrum_get_waterfallread only50/100
Get waterfall display data (power vs time/frequency)
spectrum_record_audiowrite50/100
Record demodulated audio to WAV file
spectrum_record_iqwrite50/100
Record raw IQ samples to file
CRITICAL: No output schemas documented for any of the 23 tools. LLMs have no way to know what data structure they will receive, making it impossible to chain tools or validate responses. This violates the pattern:tool requirement and breaks agent reasoning.
HIGH: Several tools lack proper enum constraints despite accepting only specific values. window parameter in spectrum_analyze has enum, but demod_mode in spectrum_record_audio should be constrained to ['AM','FM','SSB'] as enum, not free-form string.
HIGH: Error handling is minimal. SDRError class exists but no recovery guidance or actionable error messages are visible in the tool implementations. LLMs need messages like 'Device not found. Check device_index and try sdr_connect with device_index=0.'
MEDIUM: No tool descriptions mention prerequisites or dependencies. aviation_track_aircraft requires dump1090 binary, but this is not stated in the description. Users/LLMs will not know this dependency exists.
MEDIUM: Pagination and result limits are not documented. aviation_get_aircraft, marine_get_vessels, and ism_get_devices return potentially large result sets with no max_results or limit parameters visible. This can cause context window exhaustion.
Make frequency parameter accept human-friendly formats in description. E.g., 'frequency (number, Hz): Center frequency. Examples: 1090000000 for 1090 MHz, 161975000 for AIS Channel A.'
Document what happens when LLMs call stop_* tools without a corresponding start_*. E.g., aviation_stop_tracking: 'Stop tracking. No error if no tracking is active.'
Add field names to every list response. E.g., aviation_get_aircraft should document that each aircraft record has: icao_addr, callsign, altitude, latitude, longitude, velocity, heading, last_seen (timestamp).