Skip to main content
Glama

advanced_control

Destructive

Execute discovered oscilloscope controls or full-memory captures with pre-write validation, returning actual settings and partial-failure details for safe readback checks.

Instructions

Execute a discovered control or full-memory capture, requiring --allow-control.

Validates before writing; returns actual settings and any partial failure. Changes may invalidate a retained capture. Inspect readback before retrying. Settings changes do not generally roll back; decode.capture explicitly restores the previous core setup. Full-memory capture performs its documented transfer/acquisition cleanup.

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>",
      "arguments": "<arguments>"
    },
    "name": "advanced_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsYes
operationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description goes well beyond them: it validates before writing, returns actual settings plus partial-failure detail, warns that changes may invalidate a retained capture, and states that settings changes do not generally roll back while decode.capture restores the previous core setup. That non-reversibility and invalidation detail is exactly the behavior an agent needs before calling a destructive tool.

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?

The definition is dense and front-loads the most important constraint (the --allow-control requirement) before the safety caveats. Every sentence carries information, though phrases like 'its documented transfer/acquisition cleanup' and the decode.capture aside lean on context the reader may not have.

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?

There is no output schema, so the description correctly takes on the return-value burden by stating it returns actual settings and any partial failure. Combined with the rollback, invalidation, and cleanup notes, this covers a destructive two-parameter tool well; the remaining gap is the undefined vocabulary of the 'operation' parameter.

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% and the schema only exposes an unconstrained 'operation' string plus a free-form 'arguments' object with additionalProperties, so the description carries the full burden. It partially compensates by revealing the flag-style argument convention and one required flag ('--allow-control'), but it never enumerates valid operation values or explains how 'arguments' is shaped per operation.

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?

The first sentence gives a concrete verb+resource pair: it executes either a previously 'discovered control' or a full-memory capture, which implicitly ties it to the discover_operations sibling. It is clear enough to distinguish from read-only siblings like advanced_read or inspect_signal, but the generic name 'advanced_control' and the undefined term 'control' keep it from being fully self-explanatory.

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?

The description supplies a hard prerequisite ('requiring --allow-control') and an operational rule ('Inspect readback before retrying'), which is real when-to-use guidance. However, it never states when to prefer this tool over acquisition, advanced_read, or a plain settings change, and it gives no explicit exclusions, so the agent must infer the routing.

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