nk-dho924s-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DHO_HOST | No | The hostname or IP address of the NK TECHNOLOGIES DHO924S oscilloscope. | 192.168.1.174 |
| DHO_PORT | No | The TCP port used for LAN SCPI communication with the oscilloscope. | 5555 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Controls an NK TECHNOLOGIES DHO924S oscilloscope (modded Rigol DHO800/900, 4 channels) over LAN SCPI. Use screenshot to see the screen, status for settings, measure for numbers (computed from the downloaded waveform: the firmware's own :MEAS queries crash its SCPI server and are blocked). Changing settings affects the user's bench: say what you change, and restore settings you changed temporarily (status before, then set back).
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 |
|---|---|
| statusC | Identity plus acquisition, timebase, trigger and channel settings (default: all 4 channels). |
| screenshotA | Capture the scope screen as a PNG image (1024x600). |
| set_channelB | Change channel settings; only the given ones are changed. Returns the new channel state. |
| set_timebaseB | Set horizontal scale (s/div) and/or trigger position offset (s). Returns the new timebase. |
| set_triggerC | Edge trigger settings; only given ones are changed. Returns the trigger state. |
| acquireA | Run/stop/single acquisition, force a trigger, autoscale (changes many settings!) or clear the display. |
| measureB | Measure channels from one downloaded acquisition: Vpp, robust Vpp, min/max/mean, RMS, frequency (FFT), fundamental amplitude/phase, crest factor, THD+N, clipping. stop_first freezes one acquisition so channels are comparable (acquisition is resumed afterwards if it was running). |
| get_waveformB | Download the displayed record (~1000 points) of a channel. Saves time,volts CSV to a temp file and returns its path plus measurements; optionally include up to max_points_inline decimated points inline. |
| scpiA | Send a raw SCPI command. Commands ending in '?' return the answer. :MEAS:ITEM? is blocked (crashes the firmware's SCPI server). Unsupported queries time out after ~6 s and the connection is re-opened. |
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 9 tools
Most tools target clearly distinct operations: set_channel, set_timebase, set_trigger, acquire, status, and screenshot are easy to distinguish. There is some overlap between measure and get_waveform because both can return measurements, and the generic scpi tool can duplicate nearly any operation, but the descriptions give enough guidance to choose correctly.
The set_* tools follow a clean verb_noun pattern, and get_waveform fits that style, but status, screenshot, and scpi are noun-only names while acquire and measure are bare verbs. The names are readable but use mixed conventions rather than one predictable pattern.
Nine tools is well within the ideal 3-15 range for an oscilloscope-control server. Each tool covers a meaningful capability, and there are no redundant or obviously filler tools.
The surface covers the core oscilloscope workflow: status inspection, channel/timebase/trigger configuration, acquisition control, screenshot capture, measurements, waveform download, and raw SCPI for advanced cases. Minor gaps remain, such as only edge trigger support in set_trigger and no explicit setup save/recall, but the raw SCPI tool provides a workaround.