Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hackrf_transfer

Destructive

Transmit or receive raw IQ samples with a HackRF, validating frequency, power, and authorization before licensed radio operations.

Instructions

Transmit or receive raw IQ samples with a HackRF. Transmit is a licensed radio operation: confirm frequency, power, and authorization before use. 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_transfer"
  }
}

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.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so safety profile is largely covered. The description genuinely adds the licensing/authorization requirement for transmit and the engagement-namespace path semantics, which are not in annotations. That is real added value, though it omits what gets overwritten or what the tool returns on failure.

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 safety caveat following. No filler or repetition. It is efficient, though brevity comes at the cost of the parameter guidance noted above.

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?

With a 0% schema coverage and an opaque 'arguments' string array, the description leaves the agent unable to know how to invoke the tool correctly. The existence of an output schema means return values need not be explained, but the invocation contract is the bigger gap and it is unaddressed.

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% for four parameters, and the description does not compensate. The 'arguments' array is completely unexplained, even though it is the primary payload for a raw CLI wrapper, and 'stdin' is never mentioned. The only hint is 'use relative paths' and 'engagement namespace,' which loosely gestures at working_directory and engagement_id.

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: 'Transmit or receive raw IQ samples with a HackRF.' That clearly separates it from the info/sweep siblings by direction of data flow. It stops short of naming an alternative explicitly, so it is clear but not maximally differentiated.

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?

Implies usage (transmit or receive raw IQ) and adds a genuine precondition: confirm frequency, power, and authorization before transmitting. The guidance about relative paths for engagement artifacts adds operational context. However, there is no explicit statement of when to reach for this versus oc_hackrf_sweep or oc_hackrf_info, so selection still requires inference.

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