Skip to main content
Glama
nk-dho924s-mcp

nk-dho924s-mcp

by bigtimer-dev

measure

Compute per-channel oscilloscope measurements from one acquisition—Vpp, RMS, frequency, fundamental amplitude/phase, THD+N, and clipping—and optionally freeze acquisition so channels stay comparable.

Instructions

Measure channels from one downloaded acquisition: Vpp, robust Vpp, min/max/mean, RMS, frequency (FFT), fundamental amplitude/phase, crest factor, THD+N, clipping. stop_first freezes one acquisition so channels are comparable (acquisition is resumed afterwards if it was running).

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": {
      "channels": "<channels>"
    },
    "name": "measure"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelsYes
stop_firstNo
frequency_hint_hzNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does usefully disclose a real side effect — stop_first freezes an acquisition and resumes it afterwards if it was running — which is genuine behavioral context. It says nothing about what happens if no acquisition has been downloaded, error behavior, or whether measurement is local vs on-instrument.

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?

Two sentences, front-loaded with the action and measurement set, then the stop_first caveat. The metric enumeration is dense but each item is meaningful; no filler wording.

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 formatting need not be explained. However, for a 3-parameter tool with zero schema descriptions, the definition leaves frequency_hint_hz and channel addressing undocumented and only hints at the dependency on a prior acquisition.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It explains stop_first well (freeze/resume semantics), but 'channels' is only obliquely referenced by the metric list with no indication of whether items are indices or identifiers, and frequency_hint_hz is never mentioned at all despite affecting FFT interpretation.

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 resource (channels) and enumerates exactly which metrics are computed (Vpp, RMS, FFT frequency, THD+N, clipping, etc.). The phrase 'from one downloaded acquisition' implicitly distinguishes it from acquire/get_waveform, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the tool operates on 'one downloaded acquisition', suggesting data must already be captured, and stop_first is described as a way to make channels comparable. There is no explicit 'use this instead of get_waveform when...' guidance or statement of preconditions/alternatives.

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