Skip to main content
Glama
msox2014a-mcp
by SMEAC

Trigger setup and control

scope_trigger

Configure and control an oscilloscope's edge trigger by setting source, level, slope, sweep, coupling, holdoff, and noise rejection, then force, arm, or check trigger status.

Instructions

Configure and control the edge trigger.

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

Input Schema

NameRequiredDescriptionDefault
levelNoTrigger level in volts
slopeNo
sweepNoauto: free-runs without trigger | normal: waits for a trigger
sourceNo1-4/'ch1'..'ch4', 'd0'..'d7', 'ext', 'line' or 'wgen'
wait_sNoarm: seconds to wait for the trigger (0 = don't wait)
holdoffNoHoldoff in seconds (40 ns - 10 s)
couplingNo
hf_rejectNoHigh-frequency reject (50 kHz LPF)
operationYesset: configure edge trigger | get | force: force a trigger now | arm: single-shot arm (:SINGle) | status: running? triggered since last check?
noise_rejectNoNoise reject (increased hysteresis)

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?

The annotations contain only a title, so the description carries the full burden, and it discloses nothing about the five distinct operations (set/get/force/arm/status), which have very different side effects including immediate trigger forcing and single-shot arming. No mention of whether configuration is disruptive to a running acquisition or what a 'get' returns beyond the existence of an output schema.

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?

A single front-loaded sentence with zero wasted words. It is efficient, though the terseness is a symptom of missing content rather than a structural flaw.

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, multi-operation control tool with mutation and arming semantics, and the description covers none of that complexity. Even though an output schema exists and the schema documents parameters well, the operation-mode behavior and destructive/state-changing effects are left entirely unaddressed.

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 80%, with enum and unit details already documented in the schema (volts, holdoff range, source formats, operation meanings), so the schema does the heavy lifting. The description adds no additional meaning beyond that, which matches the baseline 3.

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?

States a specific verb ('Configure and control') with a specific resource ('the edge trigger'), so an agent knows this is the trigger-subsystem tool. It does not distinguish itself from siblings such as scope_configure or scope_capture, which keeps it from a 5.

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 guidance on when to use this versus scope_configure, scope_capture, or scope_measure, and no mention of prerequisites such as stopping acquisition or needing an armed/single-shot state. The agent must infer routing from the name alone.

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