Skip to main content
Glama
nk-dho924s-mcp

nk-dho924s-mcp

by bigtimer-dev

get_waveform

Download a displayed oscilloscope channel record, save time/volts CSV to a temp file, and return the file path plus measurements, with optional inline decimated points.

Instructions

Download the displayed record (~1000 points) of a channel. Saves time,volts CSV to a temp file and returns its path plus measurements; optionally include up to max_points_inline decimated points inline.

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": {
      "channel": "<channel>"
    },
    "name": "get_waveform"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYes
save_csvNo
max_points_inlineNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose a meaningful side effect — a time/volts CSV is written to a temp file whose path is returned — plus that measurements accompany the path. It says nothing about failure modes (invalid or disabled channel), whether it blocks on the instrument, temp-file lifetime, or the decimation method.

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 tight sentences with the primary action and data volume front-loaded, followed by output behavior. Minor roughness such as 'time,volts' missing a space slightly hurts readability but wastes no words.

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 values need not be spelled out, and the description usefully names the path-plus-measurements shape. However, for an instrument-reading tool with zero-annotation and zero-schema-coverage parameters, missing preconditions and error behavior leave an agent without enough to call it confidently in edge cases.

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 coverage is 0%, so the description must compensate for all three parameters. It clarifies max_points_inline (decimated points returned inline) and implies save_csv's effect (CSV written to temp file, defaulting on), but leaves save_csv=false behavior undefined and never explains channel selection or how decimation relates to the ~1000-point record.

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?

Specific verb plus resource: 'Download the displayed record (~1000 points) of a channel', including the approximate data volume and the returned artifacts. It is clearly distinguishable from measure/screenshot/acquire by naming the displayed record as the source, but it never explicitly contrasts itself with those siblings.

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 only implied: fetch raw waveform data for a channel. There is no statement of when to prefer this over 'acquire' or 'measure', and no prerequisites such as whether the channel must be enabled or acquisition running. The one piece of genuine routing guidance is the inline-vs-file choice via max_points_inline.

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