Skip to main content
Glama

acquisition

Start, stop, or arm a single capture on the Rigol DS1202Z-E; control access is required, and single mode returns before triggering.

Instructions

Start, stop, or arm a single acquisition. Requires --allow-control.

Run/single may replace an existing captured waveform. Single returns before triggering.

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": "acquisition"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the baseline already signals a non-read operation. The description adds genuinely non-derivable behavior: a permission gate (--allow-control) and the fact that run/single can overwrite an existing captured waveform, which sits in tension with destructiveHint=false but is explicitly disclosed rather than contradicted. What's missing is error behavior when the control flag is absent and what stop does to an in-flight capture.

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?

Four short sentences, front-loaded with the action set and the permission requirement, then the two behavioral caveats. The CLI-style flag notation is compact and informative, though it is the one element a model might misread as a tool argument rather than an environment prerequisite.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 no explanation, and the single-parameter schema keeps the surface small. For a mutation tool, the definition covers the permission prerequisite and the overwrite hazard, leaving only minor gaps around stop semantics and failure modes.

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 0%, and the single enum parameter is documented only by its value names, so the description has to carry the load. It does explain the effect of single (returns before triggering) and that run/single may replace an existing waveform, but never distinguishes stop from the others or clarifies the unmatched "arm" terminology.

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?

"Start, stop, or arm a single acquisition" gives a concrete verb set and a scoped resource (a single acquisition, not a stream), which separates it from siblings like waveform or status. The only weakness is that "arm" has no matching enum value, so the mapping between prose verbs and the action values is slightly ambiguous.

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

Usage Guidelines4/5

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

The definition supplies a real precondition ("Requires --allow-control") and an implicit selection rule: pick single when you don't want to block until trigger ("Single returns before triggering"). It stops short of stating when not to use this tool or what alternative handles multi-acquisition or continuous capture.

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