Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_sigrok_cli

Destructive

Capture and decode digital and analog signals from sigrok-compatible logic analyzers and oscilloscopes, running inside the selected engagement namespace with relative artifact paths.

Instructions

Capture and decode digital and analog signals with sigrok-compatible logic analyzers and oscilloscopes. Runs from the selected engagement namespace; use relative paths for engagement artifacts.

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": {
      "engagement_id": "<engagement_id>",
      "arguments": "<arguments>"
    },
    "name": "oc_sigrok_cli"
  }
}

Input Schema

NameRequiredDescriptionDefault
stdinNo
argumentsYes
engagement_idYes
working_directoryNo.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, non-idempotent, so the risk profile is known. The description adds useful context about namespace scoping and relative paths, but for a destructive tool it omits what may be overwritten, that device access is required, and that 'arguments' is passed straight through to the sigrok binary.

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?

Two short sentences, nothing wasted, with the capability stated up front and the operational constraint second. Slightly too terse for the number of undocumented parameters, but structurally sound.

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?

An output schema exists, so return values need no explanation. However, for a destructive, open-world CLI passthrough with zero schema coverage, the description leaves out critical invocation details – chiefly that the arguments array is a raw command line to the sigrok tool. The namespace/path note is a helpful but partial fill.

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% across four parameters, so the schema supplies only types and defaults. The description never explains that 'arguments' is an argv array for the underlying signal-capture binary or what 'stdin', 'engagement_id', and 'working_directory' mean; only the relative-path sentence indirectly touches 'working_directory'.

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?

States a specific verb pair (capture and decode) plus the resource (digital and analog signals) and the hardware class (sigrok-compatible logic analyzers and oscilloscopes). It does not distinguish this from any sibling, and it never says the tool is a raw CLI wrapper, but the domain is unmistakable.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternatives among the many sibling CLI tools. The only guidance is operational ('Runs from the selected engagement namespace; use relative paths'), which tells an agent nothing about when to pick this over another tool.

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