daqmx-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 |
|---|---|
| get_server_statusA | Report backend readiness, enforced safety limits, allowlist state, and project warnings. |
| list_devicesA | List only devices visible through the configured device allowlist. |
| get_device_detailsB | Get read-only capabilities for one explicit allowed device. |
| list_physical_channelsA | List allowed analog-input and/or digital-input physical channels for one device. |
| self_test_deviceA | Run NI-DAQmx's brief device self-test; it does not establish electrical safety. |
| acquire_analog_voltageA | Perform one finite, bounded analog-voltage input transaction and return statistics plus a small preview. |
| read_digital_inputsA | Read one software-timed sample from explicit digital-input lines. |
| record_analog_voltageA | Perform one finite analog input and create a new TDMS or CSV file inside the approved directory. |
| explain_daqmx_errorA | Explain a DAQmx error while preserving the supplied numeric code and original message. |
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
Every tool targets a distinct resource or action: device discovery, server status, channel listing, self-test, analog input, digital input, recording, and error explanation. The two analog voltage tools are differentiated by output (in-memory statistics vs. file creation), so no agent confusion.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_devices, get_device_details, read_digital_inputs). Even compound verbs like self_test_device and record_analog_voltage adhere to the same pattern, making the API predictable.
With 9 tools, the server is well-scoped for a DAQmx interface, covering device management, input operations, recording, and diagnostics. The count is neither sparse nor bloated, and each tool earns its place.
Core workflows are covered: device discovery, channel enumeration, analog/digital input, recording to file, self-test, and error handling. However, analog/digital output and continuous acquisition are absent, which may be intentional for safety but represents a notable gap for a DAQmx server.