Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_lsusb

Destructive

Lists USB devices visible in the container—including SDR, NFC, debug-probe, and serial adapters—to verify connected hardware for the active engagement namespace.

Instructions

List USB devices visible inside the container, including known SDR, NFC, debug-probe, and serial adapters. 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_lsusb"
  }
}

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

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the safety profile is carried by structured data. The description adds useful context about execution scope (container view, engagement namespace, relative artifact paths) but never addresses the tension between 'list' framing and the destructive/raw-exec annotations, nor that the argument array is forwarded to the underlying lsusb 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 sentences, front-loaded with what the tool returns and followed by execution context; no filler. The relative-path sentence is slightly tangential to the core purpose but still earns its place operationally.

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

Completeness2/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 prose, but for a four-parameter tool with zero schema descriptions the definition leaves the most important lever unexplained. Combined with absent when-to-use guidance, an agent can identify the tool but not confidently parameterize it.

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 description must carry the load and largely does not. It gestures at engagement_id/working_directory via the namespace and relative-path sentence, but the central 'arguments' array (lsusb flags such as -v, -t, -d) and 'stdin' get no explanation at all.

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 concrete verb and resource ('List USB devices visible inside the container') and narrows scope with the device classes it surfaces (SDR, NFC, debug-probe, serial adapters). It does not distinguish itself from related siblings such as oc_bladerf or oc_bluetoothctl, so an agent must infer when this inventory view is preferred.

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?

The only guidance is operational ('runs from the selected engagement namespace; use relative paths for engagement artifacts'), which says how to invoke it, not when. There is no statement of when to choose this over device-specific siblings, nor any prerequisite or exclusion.

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