Skip to main content
Glama
lucasgerads

LeCroy Oscilloscope MCP

by lucasgerads

scope_get_waveform

Capture time-domain waveform data from a selected channel, arm the scope if stopped, and save as .npz file for offline analysis. Returns file path and metadata; load with numpy for plotting or export.

Instructions

Capture waveform data from a channel and save it as a .npz file.

Use this when you need the time-domain signal (plotting, export, detailed analysis). For scalar results like peak voltage, frequency, or RMS, prefer scope_measure — it is faster and uses all scope points without any transfer.

If the scope is already stopped (e.g. from a previous capture), arms it first and waits for a fresh acquisition before reading. Always leaves the scope stopped after capture so the on-screen waveform matches the file.

Saves to a 'waveforms/' subfolder with an auto-generated filename, e.g.: waveforms/C1_20260329_153042.npz

Returns JSON with the file path and metadata — the raw voltage values are not embedded in the result. Load the file in Python with: import numpy as np d = np.load('/path/to/file.npz') time_s, voltage_v = d['time_s'], d['voltage_v']

Args: channel: Channel number 1–4 max_points: Maximum samples to capture (default 10000, evenly downsampled).

Transport: SCPI (binary WF? DAT1 transfer + INSPECT? WAVEDESC scaling)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYes
max_pointsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Thoroughly describes internal behavior: arming the scope if stopped, leaving it stopped, saving to a subfolder with auto-generated filenames, and returning metadata rather than raw data. Despite no annotations, all behavioral traits are disclosed.

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?

Well-structured with purpose first, then guidelines, behavior, parameter details, code example, and transport notes. Slightly verbose but every section adds value; appropriate for complexity.

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?

Covers all aspects: inputs, behavior, output (JSON with file path, metadata, no raw values), file loading example, and transport details. Output schema exists but description provides complementary info.

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

Parameters5/5

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

Adds crucial meaning beyond schema: channel range (1-4), max_points default (10000) with downsampling behavior. Compensates for 0% schema description coverage effectively.

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?

Clearly states the tool captures waveform data to a .npz file, with specific use cases for time-domain signal analysis. Differentiates from sibling scope_measure by purpose.

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?

Explicitly advises when to use scope_measure instead for scalar results, and describes automatic arming/stopping behavior. Provides clear context for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lucasgerads/lecroy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server