Skip to main content
Glama
msox2014a-mcp
by SMEAC

Configure channels / timebase / acquisition

scope_configure

Configure analog channels, timebase, acquisition modes, and digital MSO bits, then read, save, or recall setups by slot or file.

Instructions

Configure the analog channels, timebase, acquisition mode and digital (MSO) channels.

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

Input Schema

NameRequiredDescriptionDefault
slotNosave/recall: internal setup slot 0-9
labelNoChannel / digital bit label (max 10 chars)
scaleNoVolts per division
invertNoInvert channel
offsetNoVertical offset in volts (value at screen centre)
channelNoAnalog channel 1-4 (or 'ch2')
displayNoChannel / digital bit on or off
bw_limitNo20 MHz bandwidth limit
couplingNoInput coupling
file_nameNosave/recall: setup file name in the capture dir
operationYeschannel: analog channel settings | timebase | acquire: acquisition mode | digital: D0-D7 display/threshold | get: read the full configuration | save_setup / recall_setup: internal slot 0-9 or a file in the capture dir
thresholdNoDigital threshold: 'TTL' (1.4 V), 'CMOS' (2.5 V), 'ECL' (-1.3 V) or volts
time_modeNo
time_scaleNoSeconds per division (10 divisions on screen)
digital_bitNoDigital bit 0-7; omit to apply to all bits
acquire_typeNo
average_countNoAverages (2-65536) for acquire_type=average
time_positionNoTrigger-to-reference delay in seconds
time_referenceNoWhere the trigger point sits on screen
probe_attenuationNoProbe ratio, e.g. 1 or 10

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 behavioral annotations are supplied beyond the title, so the description carries the full burden. It does not disclose that configuration mutates instrument state, whether changes persist, whether acquisition is disrupted, or what permissions or side effects apply.

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 front-loaded sentence with no wasted wording. It is appropriately concise, though it could be structured around the operation modes to improve scanability for a 20-parameter tool.

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 complex tool with 20 parameters and seven operation modes, yet the description does not explain how parameters map to operations such as get, save_setup, or recall_setup. An output schema exists, so return values need not be described, but the operation-specific behavior remains incomplete.

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 schema already documents nearly all parameters in detail. The description only lists configuration categories and adds no meaning beyond the schema, which is the baseline expectation at this coverage level.

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 the specific verb "Configure" and names the resources: analog channels, timebase, acquisition mode, and digital (MSO) channels. It is clear what the tool does, but it does not distinguish itself from siblings such as scope_trigger or scope_capture.

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 gives no guidance on when to use this tool versus alternatives, nor does it state prerequisites or exclusions. It only implies that configuration is the purpose, leaving the agent to infer usage from the name and schema.

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