Skip to main content
Glama
msox2014a-mcp
by SMEAC

Capture waveforms

scope_capture

Capture triggered oscilloscope waveforms and download traces; export CSV or summary data and save display screenshots for analysis.

Instructions

Acquire and download waveforms, export them, or grab a screenshot.

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

Input Schema

NameRequiredDescriptionDefault
saveNoscreenshot: also save PNG to the capture dir
pointsNoPoints per channel to download (up to ~62.5k normal, 100k raw)
digitalNoAlso capture D0-D7 (MSO pod)
channelsNoAnalog channels, e.g. '1,2' or ['ch1','ch3']. Default '1'1
high_resNoTransfer 16-bit WORD data (useful with average/hresolution)
file_nameNoexport/screenshot file name (in capture dir)
ink_saverNoscreenshot: white background
operationYessingle: acquire a new triggered record (:DIGitize) and download it | fetch: download what the scope currently holds without re-acquiring | preview: decimated waveform arrays of the last capture | export_csv | export_summary: JSON with settings + measurements | last: summary of last capture | screenshot: PNG of the scope display | run / stop: acquisition control
timeout_sNosingle: seconds to wait for a trigger
points_modeNonormal: screen record | raw/maximum: full acquisition memory (scope stopped)normal
max_preview_pointsNopreview: max points per trace

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no behavioral annotations beyond a title, the description carries the full burden of disclosure. It states acquisition and export actions but does not mention side effects such as file writes, scope state changes, trigger waiting, or stopping the scope for raw data, leaving significant behavioral gaps.

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?

The description is a single front-loaded sentence with no wasted words. It efficiently states the core capabilities without redundancy.

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?

For a tool with 11 parameters and nine operations, the description is very sparse, though the schema compensates with detailed operation descriptions. It covers the main capture/export/screenshot uses but omits acquisition control (run/stop), preview, and fetch distinctions that an agent might need when selecting the 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?

The schema has 100% description coverage and detailed enum descriptions for every operation, so parameter meaning is fully documented there. The description adds no additional semantic detail beyond naming export and screenshot actions, making the baseline 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 uses specific verbs and resources: acquire and download waveforms, export them, and grab a screenshot. This clearly identifies the tool's capture-oriented purpose, though it does not explicitly distinguish it from sibling tools like scope_measure or scope_trigger.

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?

The description lists capabilities but provides no guidance on when to choose this tool over alternatives such as scope_measure or scope_trigger. It also omits when-not-to-use conditions and does not mention the run/stop acquisition control that the schema includes.

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