siglent-sdg-mcp

connect

Establishes a TCP connection to a Siglent SDG waveform generator and returns its device identification. Use it to verify host and port access before sending instrument commands.

Instructions

Connect to a Siglent SDG waveform generator over TCP. Returns device identification on success. Only hosts and ports allowed by the server configuration can be used.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "connect"
  }
}

Input Schema

Name	Required	Description	Default
`host`	No	IP address of the waveform generator (defaults to SIGLENT_SDG_IP or SIGLENT_IP env var)
`port`	No	TCP port (defaults to 5025)

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

B3.4/5.0

Behavior3/5

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

With readOnlyHint=false and openWorldHint=true already declared, the description adds useful context: it is a TCP connection, it returns device identification on success, and only server-configured hosts/ports are permitted. It does not say what happens if a connection already exists, whether the session persists, or how failures surface, which matter for a stateful connect operation.

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?

Three short sentences, front-loaded with the action and target. The return-value statement and the access restriction each add information, so there is minimal waste.

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?

No output schema exists, and the description only says a device identification is returned without indicating its shape. For a stateful connection tool it omits the lifecycle context (persistence of the connection, the role of the disconnect sibling) that an agent would need to use it correctly in a multi-step workflow.

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 schema already documents both the host (including the SIGLENT_SDG_IP/SIGLENT_IP env var fallback) and the port default of 5025. The description's only addition is the policy constraint that host and port must be permitted by server configuration, which is a useful constraint but not a semantic expansion of the parameters.

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 ('Connect') and a specific resource ('Siglent SDG waveform generator over TCP'), so an agent knows exactly what the call does. It implicitly separates itself from the 'disconnect' sibling, though it never names alternatives such as 'identify', which also returns identification data.

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: the agent can infer this is the prerequisite step before the configure_*/get_* tools, but the description never states that sequencing or says when not to use it. There is no explicit routing between this tool and the 'identify' sibling despite the overlapping return value.

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