siglent-sdg-mcp

get_modulation

Read-only

Retrieves all modulation parameters for a selected channel, including type, source, frequency, depth or deviation, and carrier settings, to inspect current generator modulation.

Instructions

Get the modulation parameters of a channel. Returns all modulation settings including type, source, frequency, depth/deviation, and 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": "get_modulation"
  }
}

Input Schema

Name	Required	Description	Default
`channel`	Yes	Channel to query

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.9/5.0

Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds meaningful behavioral context by enumerating what the return contains: type, source, frequency, depth/deviation, and carrier parameters. It does not cover error behavior or formatting, but that is a minor gap for a simple getter with no output schema.

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 definition is two short sentences and front-loads the tool's purpose before listing the returned settings. Every sentence contributes useful information, with no filler or redundant wording.

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

Completeness5/5

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

For a single-parameter read-only tool with full schema coverage, the definition supplies what the schema does not: the set of returned modulation settings. The readOnly annotation covers safety. No output schema exists, but the description lists the return contents well enough for an agent to know what to expect.

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%, and the sole parameter is an enum with a description, so the schema already carries the parameter semantics. The description only restates that a channel is queried and adds no new constraints, formats, or meanings beyond the schema. That warrants the baseline score of 3.

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 gives a specific verb and resource: 'Get the modulation parameters of a channel.' That makes the read purpose unambiguous, and the contrast with the sibling name configure_modulation is implicit in 'Get.' It does not explicitly distinguish itself from configure_modulation, so it falls just 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?

Usage is only implied by the word 'Get': the tool is for querying modulation settings rather than configuring them. There is no explicit guidance on when to choose this over configure_modulation, no prerequisites, and no exclusions. The definition is minimally viable but leaves routing largely to inference.

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