Skip to main content
Glama
msox2014a-mcp
by SMEAC

Built-in WaveGen

scope_wavegen

Control or query the oscilloscope's built-in waveform generator: set function, frequency, amplitude, offset, duty cycle, pulse width, load, and output on/off.

Instructions

Control the scope's built-in waveform generator (front-panel 'Gen Out' BNC).

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

Input Schema

NameRequiredDescriptionDefault
loadNoExpected load impedance
offsetNoDC offset in volts
outputNoset: also switch output on/off
functionNo
symmetryNoramp: symmetry % (0-100)
amplitudeNoVolts peak-to-peak
frequencyNoHz (sine up to 20 MHz, square/pulse 10 MHz, ramp 100 kHz)
operationYesBuilt-in 20 MHz function generator (needs DSOX2WAVEGEN licence)
duty_cycleNosquare: duty cycle % (20-80)
pulse_widthNopulse: width 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?

Annotations provide only a title, so the description carries the full behavioral burden. It identifies the physical BNC output but does not disclose that this mutates instrument state, what get/set/on/off mean behaviorally, output switching side effects, licence requirements, or safety implications.

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 single sentence is front-loaded, avoids repetition and waste, and identifies the hardware target immediately. It is appropriately concise, though it lacks any structural cues about the multiple operation modes.

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?

This is a 10-parameter hardware-control tool with four operation modes, and the description is only one generic sentence. The rich schema and output schema reduce the burden, but the description still does not explain usage distinctions, licence prerequisites, output-side effects, or when to use get versus set/on/off.

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 90%, so the input schema already documents units, function-specific limits, and parameter meanings. The description adds no parameter-specific guidance beyond what the schema provides, so the baseline of 3 is 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 a specific resource, the scope's built-in waveform generator, and the physical front-panel 'Gen Out' BNC output. The verb 'control' is broad and does not explicitly distinguish get/set/on/off behavior, but the resource is clear enough to separate it from capture, measure, trigger, and other sibling tools.

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?

It does not explain when to use this tool versus alternatives or when not to use it. It also does not describe how to choose among the operation modes or mention prerequisites such as the licence noted in the schema, leaving usage to inference.

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