Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hackrf_info

Destructive

Enumerate a HackRF SDR to report board, firmware, and serial details; run hardware inventory first and enable USB passthrough for the device.

Instructions

Enumerate a HackRF SDR and report board, firmware, and serial information. Run oc_hardware_inventory first; the device requires host USB passthrough. 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_hackrf_info"
  }
}

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

A3.6/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true and destructiveHint=true, so the safety profile is carried structurally; the description adds genuinely non-obvious operating context (host USB passthrough, execution from the selected engagement namespace). However, it never explains why a device-enumeration call is flagged destructive or what device/host state it may alter, which is precisely the kind of detail annotations cannot convey. Note the mild tension between 'enumerate and report' and destructiveHint=true, though the description does not assert a conflicting effect.

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?

Three tight sentences, front-loaded with purpose before prerequisites and environment notes; every sentence carries information. Slightly dense clause stacking ('Runs from the selected engagement namespace; use relative paths...') but no filler.

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 not be explained, and the annotations plus the prerequisite sentence cover the operational basics. What remains missing for a tool taking a free-form CLI argument array is any hint about what those arguments should contain or the expected failure mode when no device is present.

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?

Schema description coverage is 0%, so the description must compensate and it only partly does: 'Runs from the selected engagement namespace' maps to engagement_id and 'use relative paths for engagement artifacts' maps to working_directory. The 'arguments' array (a raw CLI passthrough) and 'stdin' are left completely unexplained, which is the largest semantic gap in the definition.

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 and resource ('Enumerate a HackRF SDR') plus precisely what is returned ('board, firmware, and serial information'), which is far more than the bare tool name. It does not explicitly differentiate itself from the other HackRF siblings (oc_hackrf_sweep, oc_hackrf_transfer), so an agent must infer that distinction from the verb alone.

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

Usage Guidelines4/5

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

'Run oc_hardware_inventory first' gives an explicit ordering precondition that an agent would otherwise miss, and the USB passthrough requirement is a real go/no-go condition. There is no when-not guidance and no naming of the sweep/transfer siblings as alternatives for different HackRF tasks.

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