siglent-sds-mcp

scpi_query

Read-only

Send a raw SCPI query to a Siglent SDS oscilloscope and get the returned value. Use it for queries not covered by other tools, such as *IDN? or C1:VDIV?.

Instructions

Send a SCPI query to the oscilloscope and return the response. Use this as an escape hatch for queries not covered by other tools. Only queries are accepted: a single header ending in '?' (e.g. '*IDN?', 'C1:VDIV?', 'SARA?'); parameters after '?' only for PAVA? (e.g. 'C1:PAVA? FREQ'). Note: CHDR is set to OFF, so responses contain only values (no headers).

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": {
      "command": "<command>"
    },
    "name": "scpi_query"
  }
}

Input Schema

Name	Required	Description	Default
`command`	Yes	SCPI query to send (e.g. '*IDN?', 'C1:VDIV?', 'SARA?')
`timeout_ms`	No	Timeout in milliseconds (default 5000)

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv2.0.0Nov 13, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- changedInput schema / properties / command / description
```
Previous value: -"SCPI query command to send (e.g. '*IDN?', 'C1:VDIV?', 'SARA?')"New value: +"SCPI query to send (e.g. '*IDN?', 'C1:VDIV?', 'SARA?')"
```
- addedInput schema / properties / command / maxLength
```
Added value: +512
```
- changedInput schema / properties / timeout_ms / description
```
Previous value: -"Timeout in milliseconds (default 2000)"New value: +"Timeout in milliseconds (default 5000)"
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +60000
```
- addedInput schema / properties / timeout_ms / minimum
```
Added value: +500
```
- changedInput schema / properties / timeout_ms / type
```
Previous value: -"number"New value: +"integer"
```
First observedv1.0.1May 6, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds genuine value by disclosing that CHDR is OFF and therefore responses contain only values with no headers, plus the accepted command grammar and the PAVA? parameter exception. It does not say how invalid commands, device errors, or timeouts surface beyond the schema's timeout_ms field, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the action, then the routing rule, then the syntax constraint and response-format caveat. Every clause carries information an agent needs to form a valid call; nothing is filler.

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 two-parameter read-only query tool with no output schema, the description supplies what the schema cannot: the return format (values without headers), the accepted command grammar, and the single documented exception. The only remaining complexity, error and timeout behavior, is partly handled by the schema's timeout_ms bounds.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by constraining the command shape to a single header ending in '?' and noting that parameters are only valid for PAVA?, with a concrete example ('C1:PAVA? FREQ') that the schema's example list omits. timeout_ms receives no added semantics, but its schema description is already adequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Send a SCPI query to the oscilloscope and return the response') and immediately positions it as an escape hatch for queries not covered by other tools, which separates it from siblings like measure, get_waveform, or identify. An agent can tell what this does and that it is the general fallback without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('escape hatch for queries not covered by other tools') and an explicit when-not/constraint ('Only queries are accepted: a single header ending in "?"'), including the one documented exception for parameters after '?' with PAVA?. No inference is required to decide to call this versus a specialized sibling.

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

Deploy Server