siglent-sdg-mcp

equal_phase

Synchronize the phase of both generator channels, aligning C1 and C2 for a consistent waveform relationship.

Instructions

Synchronize the phase of both channels (EQPHASE). Aligns the phase relationship between C1 and C2.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "equal_phase"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.4/5.0

Behavior2/5

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

The annotation readOnlyHint=false indicates a mutation, but the description only restates the action ('synchronize') without disclosing side effects, prerequisites, reversibility, or whether the operation is destructive. It adds no behavioral context beyond what the name and annotation already imply.

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 extremely concise—two short sentences, front-loaded with the primary action. No filler or redundancy.

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

Completeness3/5

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

For a simple, parameterless tool, the description adequately explains the core purpose. However, it fails to clarify how this differs from the related sibling 'configure_sync' or to mention any prerequisites or consequences of use. This could lead to confusion for an agent deciding between tools.

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?

There are zero parameters, so the description does not need to explain parameter meanings. The baseline of 4 is appropriate since the tool's operation is clear from the description.

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

Purpose4/5

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

The description clearly states a specific verb ('Synchronize'/'Aligns') and the resource (phase of channels C1/C2). It identifies the operation without ambiguity, but it does not explicitly differentiate from the sibling tool 'configure_sync', which might also deal with synchronization.

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?

The description implies when to use the tool (when phase alignment between C1 and C2 is needed), but it provides no explicit guidance about when not to use it or what alternatives exist. No exclusions or comparison with related tools like 'configure_sync' are given.

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