Skip to main content
Glama
msox2014a-mcp
by SMEAC

Raw SCPI

scope_scpi
Destructive

Send any raw SCPI command to the oscilloscope for actions other tools don't cover, including writes, queries, and binary block captures saved to a file.

Instructions

Send a raw SCPI command (escape hatch for anything the other tools don't cover).

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": "scope_scpi"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoauto: query if the header ends in '?', else write | binary: IEEE-488.2 block queryauto
commandYesSCPI command, e.g. ':MEASure:VPP? CHANnel1' or ':CHAN1:SCAL 0.5'
file_nameNobinary: save the block to this file

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, so the agent knows this can change instrument state. The description reinforces this by calling it 'raw' and an escape hatch, implying unvalidated pass-through, but it does not mention the binary mode writing a block to a file on disk or any side effects of arbitrary commands. With annotations covering the safety profile, this is adequate but not rich.

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 sentence with the action front-loaded and the disambiguating 'escape hatch' clause immediately after. Nothing is wasted.

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?

The tool has three parameters, an enum mode, a binary file-write path, and a destructive hint; the description addresses only the generic 'raw command' concept. Because the input schema is fully described and an output schema exists, the remaining gaps (file side effects, mode-default behavior, result handling) are tolerable but leave the definition thin for a destructive power tool.

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 schema already explains auto/write/query/binary mode semantics, the command example syntax, and the binary file_name target. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb and resource ('Send a raw SCPI command') and frames its role as the escape hatch for anything the other tools don't cover, which distinguishes it from the higher-level siblings like scope_configure and scope_measure. It does not name a specific sibling, so differentiation is generic rather than explicit.

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

Usage Guidelines4/5

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

The parenthetical gives a clear selection rule: use this when the other tools don't cover the operation. There is no explicit when-not guidance (e.g., 'prefer scope_capture for waveform reads') and no warning that a raw command can put the instrument in an unexpected state, but the core usage context is stated.

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