MHS-5200A MCP Server

Overview Schema Source Related Servers Discussions Admin

mhs5200_set_phase

Idempotent

Set the phase offset of CH2 relative to CH1 on an MHS-5200A signal generator, specifying degrees from -180 to +180 where positive values make CH2 lead CH1.

Instructions

Set the phase offset of CH2 relative to CH1.

Args: params: Phase parameters containing: - phase_deg (int): Phase offset (-180° to +180°) Positive = CH2 leads CH1 Negative = CH2 lags CH1

Returns: JSON confirming the new phase setting.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Description adds sign convention (positive = CH2 leads) beyond annotations. idempotentHint and destructiveHint are already covered. Could mention prerequisites like connection state.

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

Conciseness4/5

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

Concise but includes Args and Returns sections which are unnecessary given schema and output schema. Still compact and front-loaded with key action.

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?

Adequate for a simple setter with output schema. Could mention that it modifies device state or requires connection. Given sibling tools, completeness is reasonable.

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?

Adds meaning beyond schema by explaining positive/negative lead/lag relationship. Schema also has description, but this reinforces it. Helpful for correct agent usage.

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?

Description clearly states 'Set the phase offset of CH2 relative to CH1' with specific verb and resource. Distinguishes from siblings like set_frequency or set_amplitude.

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?

No explicit guidance on when to use this tool versus alternatives. It is implied for phase adjustment but lacks context on prerequisites or conflicts with other settings.

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

Deploy Server