msox2014a-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MSOX_RESOURCE | No | VISA resource to auto-connect on first tool call. Set to SIM to select the simulator. | |
| MSOX_LOG_LEVEL | No | Log level. Logs go to stderr. | WARNING |
| MSOX_VISA_LIBRARY | No | VISA library to use: @ivi, @py, or a path to a VISA DLL. Defaults to vendor VISA, falling back to @py. | |
| MSOX_MCP_CAPTURE_DIR | No | Directory where CSV, JSON, PNG, and setup files are written. | ~/msox2014a_captures |
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 Agilent/Keysight MSO-X 2014A mixed-signal oscilloscope (4 analog channels, 8 digital channels, optional WaveGen) over USB/LAN via VISA. Start with scope_device(operation='connect') - resource='SIM' gives a built-in simulator. Typical flow: connect -> autoscale or configure -> scope_capture (single) -> scope_measure / preview / export. scope_help(operation='quickstart') explains more.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scope_deviceC | Discover, connect to and manage the MSO-X 2014A. |
| scope_configureC | Configure the analog channels, timebase, acquisition mode and digital (MSO) channels. |
| scope_triggerC | Configure and control the edge trigger. |
| scope_captureB | Acquire and download waveforms, export them, or grab a screenshot. |
| scope_measureC | Measure amplitude/timing parameters, phase, or the spectrum of a signal. |
| scope_wavegenC | Control the scope's built-in waveform generator (front-panel 'Gen Out' BNC). |
| scope_scpiA | Send a raw SCPI command (escape hatch for anything the other tools don't cover). |
| scope_helpC | Usage guidance for this server and the MSO-X 2014A. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| characterize_signal | Characterise an unknown signal on a channel |
| wavegen_loopback | Measure a circuit's response using the built-in WaveGen |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| status_resource | Connection and run state |
| last_capture_resource | Summary of the last capture |
TDQS
Scored across 8 tools
Each tool maps to a distinct stage of scope work (connect, configure, trigger, capture, measure, wavegen), so an agent can generally pick correctly. The main soft spots are scope_measure vs scope_capture (both produce signal data) and scope_scpi, which can theoretically do anything the other tools do.
All eight tools use a uniform scope_<noun/verb> snake_case pattern with no deviations. The prefix also correctly identifies the server's instrument domain.
Eight tools is well within the sweet spot and each covers a coherent functional area: session, configuration, trigger, acquisition, measurement, wavegen, raw SCPI, help. No tool feels redundant or padded.
The core lifecycle — discover/connect, configure, trigger, capture, measure, generate — is fully covered, plus a raw SCPI escape hatch and help. Secondary areas like math/FFT setup, cursors, serial decode, or save/recall of instrument setups are absent, though SCPI can bridge them.