rigol-dho-mcp

Overview Schema Source Related Servers Discussions Admin

get_measurement

Retrieve a specified measurement item (e.g., VPP, frequency, rise time) from a channel and return its value in SI units.

Instructions

Perform an automatic measurement on a channel and return its value.

Common items: VPP (peak-to-peak), VAVG, VRMS, VMAX, VMIN, FREQuency, PERiod, RTIMe (rise time), FTIMe (fall time), PDUTy (duty cycle). Values are in SI units (V, s, Hz). A value near 9.9e37 means the measurement is invalid for the current signal.

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": {
      "item": "<item>"
    },
    "name": "get_measurement"
  }
}

Input Schema

Name	Required	Description	Default
`item`	Yes	Measurement item, one of: VMAX, VMIN, VPP, VTOP, VBASe, VAMP, VAVG, VRMS, OVERshoot, PREShoot, MARea, MPARea, PERiod, FREQuency, RTIMe, FTIMe, PWIDth, NWIDth, PDUTy, NDUTy, TVMAX, TVMIN, PSLewrate, NSLewrate, VUPPer, VMID, VLOWer, VARiance, PVRMS, PPULses, NPULses, PEDGes, NEDGes
`channel`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description transparently explains the tool reads a measurement on a channel and returns a value, including a sentinel for invalid results. It does not discuss side effects or permissions, but the behavior is straightforward.

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 plus a bullet list; front-loaded with the primary action. Every sentence adds value, no fluff.

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

Completeness4/5

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

Given no output schema, the description covers the return value format and invalid indicator. It also lists common items, but could better explain the channel range and default.

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

Parameters4/5

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

The description adds context beyond the schema by listing common items and explaining SI units and invalid value, compensating for the 50% schema coverage. However, it does not elaborate on the channel parameter beyond implying its use.

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?

The description clearly states it performs an automatic measurement on a channel and returns a value, listing common measurement items. This distinguishes it from sibling tools like get_waveform or get_status which return raw data or status.

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

Usage Guidelines3/5

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

Provides examples of common items and explains interpretation of invalid values, but does not explicitly compare to alternative tools or state when not to use it.

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

Deploy Server