Skip to main content
Glama
Sign In
siglent-sdg-mcp

siglent-sdg-mcp

by MagnusJohansson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_output

Read-only

Query a channel's output settings—on/off status, load impedance, and polarity—to verify Siglent SDG waveform generator output configuration.

Instructions

Get the output state of a channel, including on/off status, load impedance, and polarity.

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

Input Schema

NameRequiredDescriptionDefault
channelYesChannel to query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.4
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safe read behavior is covered. The description adds the returned fields, but it does not discuss permissions, error behavior, or return structure beyond that list.

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?

A single front-loaded sentence with no redundant wording. Every phrase contributes to purpose or return content.

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

Completeness4/5

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

For a simple one-parameter read-only getter with annotations and full schema coverage, the description is nearly complete, especially because it lists the returned fields. It could still state the return structure or error behavior, which is why it is not a 5.

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?

The single channel parameter is fully described by the schema, including its C1/C2 enum and 'Channel to query' description. The tool description mentions 'a channel' but adds no further semantics beyond the schema.

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 uses a specific verb, 'Get,' and resource, 'output state of a channel,' and names the returned fields: on/off status, load impedance, and polarity. It is clear but does not explicitly differentiate itself from sibling tools such as configure_output.

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 guidance on when to use this tool versus alternatives like configure_output, nor any prerequisite or context for querying output state. Usage is only inferable from the verb 'Get.'

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

Deploy Server

Other Tools