Skip to main content
Glama
Sign In
rigol-dho-mcp

rigol-dho-mcp

by mattjax16
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

scpi_command

Send arbitrary SCPI commands to control and query Rigol DHO800/DHO900 oscilloscopes. Use for functions not covered by dedicated tools like cursors, math, or decoding.

Instructions

Send an arbitrary SCPI command from the DHO800/900 programming guide.

Commands ending in '?' are treated as queries and their response is returned; others are write-only. Use for anything not covered by the dedicated tools (cursors, math, decoding, mask tests, DVM, etc.).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "scpi_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesRaw SCPI command, e.g. ':CHANnel1:SCALe 0.1' or ':ACQuire:SRATe?'

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It discloses that commands ending in '?' are treated as queries with response returned, others are write-only. However, it could mention potential error handling or restrictions, but is mostly adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose. No wasted words. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Has output schema, so return values are covered. Description is complete for a generic SCPI command tool, given sibling tools cover specific functions. Tells exactly what it does and when to use it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a good description for the 'command' parameter. Description adds context about query vs write-only but doesn't add much beyond schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it sends arbitrary SCPI commands from a specific programming guide. It distinguishes from dedicated tools by specifying 'use for anything not covered by the dedicated tools'. The description also clarifies query vs write-only behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use this tool (for anything not covered by dedicated tools) and describes the behavior for queries vs write-only. It references a specific programming guide, providing clear guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools