Skip to main content
Glama
msox2014a-mcp
by SMEAC

Scope device / connection

scope_device

Discover, connect to, and manage an MSO-X 2014A oscilloscope via VISA: list instruments, open/close sessions, check status, identity, options, reset, clear, autoscale, and read errors.

Instructions

Discover, connect to and manage the MSO-X 2014A.

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": {
      "operation": "<operation>"
    },
    "name": "scope_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
probeNolist: query *IDN? of Keysight/LAN instruments
resourceNoVISA resource for connect, e.g. 'USB0::0x0957::0x1798::MY12345678::INSTR', 'TCPIP0::192.168.1.50::inst0::INSTR', or 'SIM' for the simulator. Omit to use $MSOX_RESOURCE or auto-detect.
operationYeslist: find VISA instruments | connect | disconnect | status: run state + main settings | identify: *IDN? | options: installed licences | reset: *RST factory default | clear: *CLS | autoscale: front-panel Auto Scale | errors: drain the scope error queue
timeout_sNoconnect: I/O timeout in seconds

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose that 'reset' invokes *RST factory defaults, that 'autoscale' changes front-panel settings, that 'disconnect' ends the session, or that a VISA resource may need authentication/configuration. It is not misleading, but it is largely silent on behavior beyond the tool's broad purpose.

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?

The description is a single efficient sentence with no filler, and the core action is front-loaded. It is perhaps too terse for the tool's complexity, but that is a completeness issue rather than a conciseness defect.

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

Completeness2/5

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

The tool has ten operations including destructive ones (reset, autoscale, disconnect), four parameters, and no annotations. A single sentence does not adequately convey the tool's role as the connection and management entry point, nor does it warn about state-changing operations. The output schema and detailed operation enum help, but the description remains thin for the complexity.

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 operation enum individually documents all ten operations, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond what is already structured, making the baseline of 3 appropriate.

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 states specific verbs and a resource: 'Discover, connect to and manage the MSO-X 2014A.' It is clear what the tool is for, but it does not distinguish this tool from siblings like scope_scpi, scope_help, or scope_configure, which also relate to the same instrument. The broad 'manage' is clarified only by the schema's operation enum, not by the description itself.

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 when-to-use guidance, no mention of alternatives such as scope_scpi, and no prerequisites stated (e.g., whether connect must precede capture). The operation enum in the schema implies per-operation usage, but the description offers no routing logic for an agent choosing among sibling tools.

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