Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hackrf_sweep

Destructive

Sweeps a frequency range with a HackRF and reports observed power levels, helping you assess spectrum activity within the selected engagement workspace.

Instructions

Sweep a frequency range with a HackRF and report observed power levels. 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_sweep"
  }
}

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 destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description contributes the engagement-namespace scoping and relative-path convention, which is real added context. It says nothing about hardware requirements, whether the radio is left in a given state, or runtime/throughput characteristics of a sweep, so it remains thin for a destructive open-world tool.

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 compact sentences with the core action front-loaded and the namespace/path constraint second; nothing is redundant. It is arguably too terse rather than bloated, but there is no wasted wording.

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?

The tool wraps a hardware CLI with an opaque argument-array parameter at 0% schema coverage, and the description supplies neither the argument syntax nor the hardware/prerequisite expectations. The existing output schema relieves it of explaining return values, but for a destructive, non-idempotent open-world tool the definition leaves too much for the agent to guess.

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. Only a passing hint about relative paths touches working_directory; engagement_id, the raw string array "arguments", and stdin are entirely unexplained, and for an "arguments" passthrough an agent has no way to know the expected CLI flag format.

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?

"Sweep a frequency range with a HackRF and report observed power levels" gives a specific verb (sweep), a specific resource (HackRF radio), and the nature of the output (power levels). It is clear on its own, but it never distinguishes itself from the sibling tools oc_hackrf_info and oc_hackrf_transfer, so the agent must infer that this is the spectrum-scanning one rather than the device-info or file-transfer one.

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 usage context is the operational note that it runs from the selected engagement namespace and should use relative paths for engagement artifacts. There is no statement of when to choose this over oc_hackrf_info or oc_hackrf_transfer, no prerequisites (connected HackRF hardware, an established engagement), and no exclusions.

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