Skip to main content
Glama

characterize_signal

Runs a full characterization loop on an oscilloscope channel to discover signal parameters and confidence, with optional PNG export of the fitted capture.

Instructions

Characterize the signal on channel — the FLAGSHIP goal-level tool.

Runs the probe → vertical fit → horizontal fit → trigger hunt → characterize
loop, settling and re-verifying after each adjustment (bounded by
:data:`MAX_SETTLE_ITERATIONS`). Returns the discovered signal parameters, a
full measurement snapshot, and a confidence flag. When ``export_path`` is
given, the deep-memory capture is rendered to a PNG there.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYesAnalog channel to characterize, 1-based (1–4).
export_pathNoOptional filesystem path to render the fitted deep-memory capture to a PNG. None skips the export.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description details the iterative algorithm, settling, and re-verification, which goes beyond the minimal. No annotations exist, so the description carries the full burden. It does not explicitly mention side effects or permissions, but the process seems non-destructive. The behavioral description is fairly thorough.

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 description is front-loaded with the core purpose and then explains the process and outputs. It is concise but includes all necessary details. A minor improvement could be slightly more brevity, but it is well-structured.

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?

Given the tool's complexity (multi-step loop with settle iterations) and the presence of an output schema covering return values, the description provides a good overview. It covers the algorithm, what it returns, and the optional export. It is reasonably complete, though it could elaborate on the confidence flag or iteration bound.

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?

The description mentions both parameters ('channel' and 'export_path') and provides context, but the input schema already covers them with 100% coverage. The description does not add significant semantics beyond what the schema descriptions offer, so it meets the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it characterizes the signal on a channel and is the 'FLAGSHIP goal-level tool'. It details the multi-step algorithm (probe, vertical fit, etc.) and distinguishes itself from simpler sibling tools like 'measure' or 'acq_run' by being comprehensive and iterative.

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 calls it the 'FLAGSHIP goal-level tool', implying it is the primary tool for signal characterization, but it does not explicitly state when to use simpler alternatives or when not to use this tool. It lacks explicit usage guidance compared to alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/armchairdeity/mcp-server-scpi'

If you have feedback or need assistance with the MCP directory API, please join our Discord server