MHO98 MCP Server

Overview Schema Source Related Servers Discussions Admin

set_trigger_setup_hold

Configure oscilloscope Setup & Hold triggering by defining data and clock sources, edge slope, pattern, timing, and voltage levels to capture signal violations.

Instructions

Setup & Hold trigger (:TRIGger:MODE SETup, subsystem :TRIGger:SHOLd).

data_source/clock_source: CH1..CH4 or D0..D15 (data and clock lines); slope: POSitive|NEGative (clock edge); pattern: H|L (level the data must hold stable across the clock edge); condition: SETup|HOLD|SETHold; setup_time/hold_time: 1 ns .. 10 s; data_level/clock_level: volts (analog: ±4.5×scale−offset; digital: ±15 V).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`extra`	No
`slope`	No
`pattern`	No
`condition`	No
`hold_time`	No
`data_level`	No
`setup_time`	No
`clock_level`	No
`data_source`	No
`clock_source`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully documents allowed values and ranges for most parameters, but does not describe side effects such as whether the instrument must be stopped, whether this activates the trigger, or how it interacts with other trigger settings.

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 compact and front-loaded with the trigger type and SCPI subsystem, followed by a clean semicolon-separated parameter reference. Every line contributes useful semantic detail without redundancy.

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?

An output schema exists, so return values need not be explained. The parameter semantics are thorough, but for a 10-parameter SCPI trigger configuration tool with no annotations, the description omits usage context and behavioral side effects, leaving a small completeness gap.

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?

Schema description coverage is 0%, but the description compensates excellently by defining the meaning, allowed values, units, and constraints for 9 of 10 parameters, including enums (POSitive|NEGative, H|L, SETup|HOLD|SETHold), time ranges (1 ns .. 10 s), and analog/digital voltage limits. Only the generic 'extra' parameter is undocumented.

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?

It identifies the exact trigger mode 'Setup & Hold trigger' and the underlying SCPI subsystems (:TRIGger:MODE SETup, :TRIGger:SHOLd), which distinguishes it from sibling trigger configuration tools like set_trigger_edge or set_trigger_pattern. The tool name supplies the verb, and the description confirms the specific resource.

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

Usage Guidelines2/5

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

The description lists parameter semantics but gives no guidance on when to use this tool versus alternatives, no prerequisites, and no conditions that would select it over other trigger types. An agent must infer usage context from the tool name and sibling list.

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

Deploy Server