siglent-sdg-mcp

configure_sync

Configure the sync output signal for a specified channel, setting its state and sync source type to align auxiliary outputs with the generator's waveform and modulation settings.

Instructions

Configure the sync output signal for a channel.

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": {
      "channel": "<channel>",
      "state": "<state>"
    },
    "name": "configure_sync"
  }
}

Input Schema

Name	Required	Description
`type`	No	Sync source type
`state`	Yes	Sync output state
`channel`	Yes	Channel to configure

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.4Nov 14, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.0.0Aug 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations only supply readOnlyHint=false, confirming this is a mutation, and the description adds nothing beyond that. It does not state whether enabling sync affects other channel settings, whether the change persists until reset, or whether the optional 'type' parameter defaults to something when omitted.

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?

A single front-loaded sentence with zero filler or redundancy. It is efficient, though its brevity is partly a symptom of under-specification rather than disciplined editing.

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

Completeness2/5

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

For a state-mutating tool with no output schema and only a bare readOnlyHint, the description should disclose side effects, persistence, or required device state. The rich enum schema covers the inputs, but the behavioral side of the call is entirely undocumented.

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

Parameters3/5

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

Schema coverage is 100% with descriptions and enums on all three parameters, so the schema already carries parameter meaning and baseline 3 applies. The description could have added value by explaining what happens when the optional 'type' is omitted while 'channel' and 'state' are required, but it does not.

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 names a specific verb and resource ('Configure the sync output signal') scoped to a channel, which cleanly separates it from siblings like configure_modulation or configure_burst. It stops short of explicitly contrasting with configure_output, so the differentiation is implicit rather than stated.

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?

There is no when-to-use guidance, no prerequisites (e.g., whether the channel must already be configured via configure_output first), and no mention of alternatives. The agent must infer usage entirely from the name and enum values.

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