siglent-sdg-mcp

configure_modulation

Set channel modulation state, type, and parameters to generate AM, FM, PM, PWM, ASK, FSK, or PSK signals on a Siglent SDG generator.

Instructions

Configure modulation on a channel. Set state first (ON), then type and parameters. Commands are sent sequentially: state, then type, then type-specific parameters, then carrier parameters.

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>"
    },
    "name": "configure_modulation"
  }
}

Input Schema

Name	Required	Description
`type`	No	Modulation type
`depth`	No	AM modulation depth in % (0-120)
`state`	No	Modulation state. Must be ON before setting other params.
`source`	No	Modulation source (availability depends on type)
`channel`	Yes	Channel to configure
`mod_wave`	No	Modulating waveform shape (only when source is INT)
`polarity`	No	PSK polarity
`deviation`	No	FM frequency deviation in Hz, or PM phase deviation in degrees (0-360), or PWM duty deviation in %
`frequency`	No	Modulation frequency in Hz (AM/FM/PM/PWM) or key frequency (ASK/FSK/PSK)
`carrier_phase`	No	Carrier phase in degrees (0-360)
`hop_frequency`	No	FSK hop frequency in Hz
`carrier_offset`	No	Carrier DC offset in volts
`carrier_waveform`	No	Carrier waveform type
`carrier_amplitude`	No	Carrier amplitude in Vpp
`carrier_frequency`	No	Carrier frequency in Hz

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

A3.6/5.0

Behavior4/5

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

Annotations only say readOnlyHint=false; the description adds genuinely valuable behavior beyond that: commands are sent sequentially in a fixed order (state, type, type-specific parameters, carrier parameters), which matters for a stateful instrument. It stops short of disclosing persistence, error behavior, or whether omitted parameters retain prior values.

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?

Four short sentences, front-loaded with the core action followed by the invocation order. No filler, though the final sentence overlaps with the third.

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 15-parameter mutation tool with no output schema, the description covers ordering but leaves gaps: whether unspecified parameters are reset or preserved, whether each call must resend all values, and what a failure or partial application looks like.

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 description coverage is 100%, so the schema already documents each parameter's units, ranges, enums and type dependencies. The description adds only the ordering grouping (type-specific vs carrier parameters) and the state-before-others rule, which the schema also states for 'state'. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Configure modulation on a channel'), which is clearly distinguishable from siblings like get_modulation, configure_basic_wave, configure_burst and configure_sweep. It does not explicitly name or exclude any sibling, so it falls short of a 5.

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?

Gives procedural guidance for how to invoke it ('Set state first (ON), then type and parameters') but no when-to-use versus alternatives, no exclusions, and no mention of prerequisites like connecting to the instrument first. Usage is implied rather than stated.

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