Skip to main content
Glama

Decode Signal Recording

decode_signal_recording
Idempotent

Decode existing local logic or signal recordings on Linux with explicit sigrok decoder stacks, channels, and options; optionally select annotations and page output for file-only analysis.

Instructions

Decode an existing local logic/signal recording on Linux with sigrok-cli 0.7.2 and util-linux prlimit. Supply decoder stack, channels and options explicitly; optionally select input format and annotation classes. Return 50 literal output lines by default, with line_offset/line_limit paging; line_limit:null requests all remaining lines. Output windows count display lines, not annotations or samples, and do not shorten decoding. Preserve selected text, sample ranges, stderr, source/tool identity and coverage inline. Configure absolute REA_SIGROK_COMMAND. File-only analysis; no hardware acquisition or device communication. Empty output does not prove absence of traffic.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "/artifacts/uart.vcd",
      "decoders": "uart:rx=RX:baudrate=9600",
      "annotations": "uart=rx-data",
      "input_format": "vcd"
    },
    "name": "decode_signal_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute local recording path
decodersYessigrok decoder stack, options and channel assignments, e.g. uart:rx=RX:baudrate=9600
line_limitNoReturn at most this many output lines; default 50. Null explicitly returns all remaining lines within producer limits. Lines are not annotation counts.
annotationsNoOptional annotation selection, e.g. uart=rx-data
line_offsetNoSkip this many literal LF-separated output lines; default 0
input_formatNoExplicit sigrok input format and options; omitted means autodetection

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Adds substantial context beyond annotations: the decode runs via an external binary, requires an env-configured command path, windows are line-based, paging does not truncate decoding, stderr and coverage are echoed back, and empty output is not proof of absence. Safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true) is broadly consistent with the described side-effect-free file analysis.

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?

Front-loaded with the action and toolchain, then constraints, then return-format behavior. Dense but almost every clause carries information an agent needs; a few could be trimmed (e.g. repeated line-window caveats).

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?

With no output schema and 6 params, the description does the work of explaining return shape, paging, and inline preservation of stderr/coverage. Remaining gaps are minor, such as what happens on decoder errors or version-mismatch failures.

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 100%, so baseline is 3, but the description adds real meaning: line_offset/line_limit page literal output lines, 'line_limit:null requests all remaining lines', and windows 'count display lines, not annotations or samples'. This disambiguates the paging params beyond their schema text.

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?

Names a specific verb and resource ('Decode an existing local logic/signal recording') and pins the toolchain (sigrok-cli 0.7.2, prlimit). Scoping language ('File-only analysis; no hardware acquisition or device communication') separates it from capture-oriented siblings without naming any.

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?

Provides prerequisites ('Supply decoder stack, channels and options explicitly'; 'Configure absolute REA_SIGROK_COMMAND'), which tells the agent how to call it. It does not state when to prefer this over another decode/analysis tool or when not to use it, so routing guidance is only implied.

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

Deploy Server

Other Tools