siglent-sds-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| connect_tcpC | Connect to the oscilloscope through raw TCP SCPI socket. |
| disconnect_tcpA | Disconnect the current raw TCP oscilloscope session. |
| identify_tcpB | Query *IDN? through the connected raw TCP session. |
| safe_scpi_query_tcpA | Send a read-only SCPI query ending in '?' through raw TCP. |
| get_channel_tcpB | Query a channel configuration through the TCP adapter. |
| configure_channel_tcpC | Configure a channel using SDS-style TCP SCPI candidate commands. |
| configure_acquisition_tcpD | Configure acquisition/timebase/trigger using SDS-style candidate commands. |
| get_acquisition_status_tcpA | Query acquisition state, timebase, sample rate and trigger status. |
| measure_tcpD | Take a measurement using SDS-style candidate commands. |
| auto_setup_tcpC | Auto setup one channel and leave the waveform visible by default. |
| screenshot_tcpC | Capture a screen image through candidate |
| get_waveform_tcpC | Download waveform data and save CSV. capture_mode="immediate" skips WFSU and reads WF? DAT2 from the current stopped frame. Use capture_mode="configured" only for stable/repetitive signals where WFSU-selected waveform memory is desired. |
| capture_uart_auto_tcpA | Capture UART waveform and auto-decode with full self-calibration. Features
Parameterschannel: Oscilloscope channel (default C1). baudrate: Nominal baud rate. 0 = auto-detect. probe_attn: Probe attenuation factor (1 or 10). max_bytes: Estimated maximum message length in bytes (for TDIV sizing). timeout_s: Seconds to wait for a valid trigger. max_trigger_attempts: Re-ARM attempts before giving up. min_pkpk_v: Minimum PKPK (V) to accept a trigger as genuine. |
| capture_uart_2mbps_tcpC | One-shot candidate workflow for 2 Mbps UART capture and CSV analysis. |
| auto_find_waveform_tcpD | Backwards-compatible multi-channel auto setup entry point. |
| analyze_uart_csv_fileC | Analyze a two-column UART waveform CSV: time_s, voltage_v. |
| analyze_rs485_pair_csv_fileC | Analyze two CSV waveforms as RS485 A/B and compute Vdiff = VA - VB. |
| modbus_rtu_timingA | Calculate Modbus RTU character time and silence intervals. |
| generate_reportB | Generate a Markdown field report from captured artifacts and JSON summaries. |
| project_statusC | Return implementation status and verification boundary. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Most tools have clear, distinct purposes, but there is some overlap between auto_setup_tcp and auto_find_waveform_tcp, and between the two UART capture tools. However, detailed descriptions help differentiate them, so confusion is limited.
The '_tcp' suffix is consistently used for oscilloscope communication tools, but naming patterns vary (e.g., modbus_rtu_timing and project_status are noun-first, while others are verb-first). This mixed style is readable but not fully predictable.
With 20 tools, the set is at the heavy end for a specialized server, but each tool serves a specific function. Some tools like capture_uart_2mbps_tcp and auto_find_waveform_tcp feel niche or redundant, suggesting the count could be slightly trimmed.
Core oscilloscope operations (connect, configure, measure, capture, screenshot) are well covered, and there are dedicated analysis tools for UART, RS485, and Modbus. However, there is no explicit RS485 capture tool, and some operations like separate trigger configuration are bundled into broader tools, leaving minor gaps.