tinysa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TINYSA_PORT | No | Specifies the serial port of the tinySA device. If not set, USB detection is automatic. | |
| TINYSA_EXPORT_DIR | No | The directory where measurement artifacts (CSV and metadata) are exported. Defaults to 'readings' under the server's working directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | List serial ports and USB candidates. Does not connect; STM32 IDs can also be NanoVNAs. |
| get_device_infoB | Connect lazily, verify tinySA identity, and report firmware and maximum scan points. |
| get_statusA | Read sweep state, bandwidth, attenuation, display units, and processing settings. |
| capture_spectrumB | Snapshot current actual dBm trace; briefly pause and restore previous running state. Does not guarantee a fresh scan. save writes CSV and metadata to the export directory. |
| scan_spectrumA | Acquire a new dBm spectrum with paired frequencies/levels; default leaves device paused. |
| configure_measurementA | Explicitly set bandwidth in Hz, attenuation in dB, or dBm display units; read back settings. Firmware rounds bandwidth to available filters. None leaves a setting unchanged. Auto and explicit value are mutually exclusive. Changes are not rolled back on error. |
| find_spectrum_peaksB | Snapshot current trace and find strongest sampled local maxima; temporarily pauses readout. |
| pause_sweepA | Pause the displayed sweep explicitly. |
| resume_sweepA | Resume the instrument's configured display sweep (including frequency array restoration). |
| disconnect_deviceA | Release USB; the next device tool reconnects. Does not change the current sweep state. |
| get_console_helpA | Read the connected firmware's actual supported console commands. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| guide | Measurement semantics, units, state effects, CSV schema, and USB troubleshooting. |
| export_directory | Local directory used for measurement artifacts. |
TDQS
Scored across 11 tools
The sweep-control pair (pause_sweep/resume_sweep) and lifecycle tools (list_devices/get_device_info/disconnect_device) are clearly distinct. However, capture_spectrum, scan_spectrum, and find_spectrum_peaks all deal with trace acquisition and could be confused, though the descriptions do clarify snapshot vs. fresh scan vs. peak analysis.
All tools use consistent snake_case verb_noun or verb patterns (list_devices, get_status, configure_measurement, scan_spectrum). No mixed conventions or vague single-word verbs.
11 tools is well-scoped for a device-control server, covering connection, status, configuration, acquisition, and sweep control without redundancy.
The surface covers the full device lifecycle: list, connect/info, disconnect, status, configuration, acquisition, pause/resume, and console help. Minor gaps exist (configuration is limited to bandwidth/attenuation/units with no broader settings, and saving is folded into capture_spectrum rather than a dedicated export tool).