siglent-sdg-mcp

get_sweep

Read-only

Retrieve a channel's sweep settings, including state, time, start/stop frequencies, mode, direction, trigger source, carrier, and marker, to inspect or verify sweep configuration.

Instructions

Get the sweep parameters of a channel, including state, time, start/stop frequencies, sweep mode, direction, trigger source, carrier settings, and marker.

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_sweep"
  }
}

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

Behavior3/5

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

readOnlyHint=true already establishes the safe-read profile, so the description's added value is the list of sweep attributes returned (state, frequencies, mode, direction, trigger source, carrier, marker). With no output schema, that enumeration is useful, but it gives no units, value formats, or behavior when a sweep is disabled, leaving real gaps.

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?

One front-loaded sentence with the resource and scope stated first, followed by the field list. The trailing enumeration is a mild laundry list but each item is informative for a getter with no output schema.

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 getter, the description states the scope (one channel) and the full set of returned attributes, which substitutes for the missing output schema. Nothing essential to invoking it correctly is absent.

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% and the single channel parameter is fully described with an enum of C1/C2, so the schema carries the parameter semantics. The description adds nothing about the channel argument, which is acceptable at this coverage level but earns only the baseline.

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?

Specific verb+resource ('Get the sweep parameters of a channel') with an enumeration of the returned fields, so the agent knows exactly what data this yields. It does not name the complementary configure_sweep tool, so the setter/getter distinction must be inferred from the name alone.

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: 'Get' plus readOnlyHint makes clear this is a query rather than a configuration action. There is no explicit statement of when to call this instead of configure_sweep, nor any prerequisite or exclusion noted.

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