Skip to main content
Glama
msox2014a-mcp
by SMEAC

Measurements & FFT

scope_measure

Measure signal amplitude, timing, phase, and FFT spectrum from oscilloscope captures, or run scope-side measurements and list available measurement types.

Instructions

Measure amplitude/timing parameters, phase, or the spectrum of a signal.

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

Input Schema

NameRequiredDescriptionDefault
itemsNoscope: measurement names (see 'list')
pointsNofresh: points to capture
windowNofft windowhann
channelNoChannel 1-4 (default: every analog trace in the capture, or CH1)
n_peaksNofft: number of spectral peaks to report
channel2NoSecond channel for phase/delay
operationYesall: compute measurements on the last capture (host-side) | fresh: capture now, then compute | scope: use the scope's own :MEASure engine on the live acquisition | fft: spectrum/peaks/THD of the last capture | phase: phase & delay channel->channel2 on the last capture | list: available measurement names
include_spectrumNofft: include a decimated dBV spectrum

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?

Only a title annotation is supplied, so the description carries the full burden of behavioral disclosure, and it discloses nothing: notably it never says that 'fresh' actually acquires a new capture, which changes instrument/state behavior, nor whether measurement requires a prior capture or specific setup. No mention of auth, side effects, or what happens when no capture exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with zero filler and a clear lead verb, so nothing is wasted. But for a tool with six operation modes and eight parameters, one sentence is under-specified rather than appropriately concise.

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?

An output schema exists, so return-value explanation isn't required, and the schema documents the operation modes well. Still, given no behavior annotations and a mutation-adjacent 'fresh' path, the definition leaves the agent without guidance on mode selection or preconditions — adequate but with clear gaps.

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 100% and the enum descriptions for `operation` are unusually informative, so the schema does the heavy lifting. The description adds no parameter meaning beyond the schema — no clarification of units, channel defaults, or how `items` interacts with `operation` — so the baseline 3 applies.

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 ('Measure') and names the resources measured: amplitude/timing parameters, phase, and spectrum. That is clear enough to know what the tool returns, but it says nothing about the multi-operation nature (all/fresh/scope/fft/phase/list) or how it differs from siblings like scope_capture, which 'fresh' overlaps with.

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 when-to-use guidance at all — nothing tells the agent when to measure versus capture first, or which sibling to reach for. The only routing information lives in the `operation` enum description inside the schema, not in the description itself.

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