Skip to main content
Glama
kitour

RIGOL MHO98 MCP

by kitour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

measure_between

Measure delay or phase between two oscilloscope channels, using one channel as reference to compare against another. Returns edge-specific delay in seconds or phase in degrees.

Instructions

Query a two-source delay or phase measurement between two channels. source1 is the reference channel, source2 is the measured channel. DS1000Z items: RDELAY (rising-edge delay, seconds), FDELAY (falling-edge delay, seconds), RPHASE (rising-edge phase, degrees), FPHASE (falling-edge phase, degrees). DHO series exposes a 4-way matrix: RRDELAY/RFDELAY/FRDELAY/FFDELAY and RRPHASE/RFPHASE/FRPHASE/FFPHASE (first letter = source1 edge, second = source2 edge). On DHO the DS1000Z names are auto-mapped to their homogeneous equivalents (RDELAY→RRDELAY, FDELAY→FFDELAY, RPHASE→RRPHASE, FPHASE→FFPHASE). For stable readings: on DS1000Z, stop acquisition first. On DHO, keep acquisition running (see measure for details). A 9.9E37 result is the scope's invalid/overflow sentinel and comes back annotated; any source channel whose display is OFF is auto-enabled first (noted in the result). Do not call concurrently with any other rigol tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemYes
source1YesReference channel
source2YesMeasured channel

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses the 9.9E37 invalid sentinel, auto-enabling of off channels, platform-specific mapping behavior, and the concurrency restriction. These are exactly the non-obvious behaviors an agent needs to know before calling.

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?

The description is long but every sentence carries operational value: purpose, platform differences, sentinel behavior, side effects, and concurrency warning. It is front-loaded with the core purpose and then layers necessary detail without repetition or filler.

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?

For a tool with no annotations and no output schema, the description is remarkably complete. It covers parameter semantics, platform-specific behavior, invalid-result handling, side effects, and concurrency constraints. An agent has enough information to invoke the tool correctly and interpret unusual results.

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

Parameters5/5

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

The schema covers source1 and source2 with descriptions, but `item` has no description. The description compensates by explaining the DS1000Z item names, the DHO 4-way matrix, and the auto-mapping between them. This is essential semantic detail beyond the raw enum values.

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 opens with a specific verb and resource: 'Query a two-source delay or phase measurement between two channels.' It immediately distinguishes source1 as reference and source2 as measured, and the item list clarifies exactly what is being measured. This clearly differentiates it from sibling tools like measure or get_cursor_values.

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

Usage Guidelines4/5

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

The description gives clear operational context: stop acquisition on DS1000Z, keep it running on DHO, and never call concurrently with other rigol tools. It references `measure` for details, implying a relationship, but it does not explicitly state when to choose this tool over a sibling. Still, the context is strong enough for an agent to use it appropriately.

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