Skip to main content
Glama
nk-dho924s-mcp

nk-dho924s-mcp

by bigtimer-dev

acquire

Manage oscilloscope signal capture: start, stop, or run a single measurement, force a trigger, autoscale settings, or clear the display.

Instructions

Run/stop/single acquisition, force a trigger, autoscale (changes many settings!) or clear the display.

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": {
      "action": "<action>"
    },
    "name": "acquire"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It does disclose a genuine side effect – autoscale 'changes many settings!' – which is valuable beyond any structured field, but it omits the other consequences: whether stop halts a running acquisition, whether single waits for completion, whether force overrides the configured trigger condition, and whether clear destroys display data.

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

Conciseness5/5

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

A single front-loaded sentence listing operations with a well-placed parenthetical warning. No filler, no redundant restatement of the tool name.

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?

The presence of an output schema removes the need to describe return values, and a one-parameter enum tool is simple. However, for a state-changing instrument control tool with no annotations, the description should say more about side effects and ordering than a single clause on autoscale.

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

Parameters4/5

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

Schema coverage is 0%, but the enum of six self-named actions means the description's enumeration of run/stop/single/force/autoscale/clear is effectively the parameter documentation. It adds real meaning for 'autoscale' by warning it mutates many settings, which the bare enum value does not convey; only 'force' and 'single' lack explanatory detail.

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?

Description names concrete operations on a specific resource domain: run/stop/single acquisition, force a trigger, autoscale, and clear the display. These map one-to-one to the action enum, so an agent knows exactly what the tool controls. It stops short of distinguishing itself from siblings such as set_trigger or get_waveform, so it is clear but not differentiating.

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 through the enumerated actions – there is no statement of when to call acquire versus siblings like set_trigger or get_waveform, and no explanation of sequencing (e.g., run then read the waveform). The autoscale parenthetical hints at caution but gives no exclusion or prerequisite.

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