Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_rtl_power

Destructive

Run rtl_power scans from the OpenCyber RF toolkit inside an engagement namespace, passing argv tokens directly without shell parsing and using relative paths for artifacts.

Instructions

Run rtl power from the OpenCyber rf toolkit. The container executes rtl_power directly with the supplied argv tokens; shell parsing is never used. 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_rtl_power"
  }
}

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

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

The annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is largely covered. The description adds genuinely useful context beyond that: argv tokens are passed directly with no shell parsing, and execution is scoped to the selected engagement namespace. It does not explain what destructive effects are possible or what the run produces, leaving a gap against the destructive flag.

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 and followed by execution-safety and path guidance. Nothing is redundant, though the sentences are slightly telegraphic rather than explanatory.

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, and the shell-parsing and namespace notes are valuable for a destructive, open-world executor. However, for a tool flagged destructive with zero schema description coverage, the definition should say more about execution effects and all four parameters to be complete.

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 coverage is 0%, so the description must carry parameter meaning, and it only partially does: 'supplied argv tokens' maps to `arguments`, 'engagement namespace' hints at `engagement_id`, and 'relative paths' relates to `working_directory`. The `stdin` parameter is never mentioned and no format for the argv array is given.

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?

The description gives a specific verb (run) and a specific underlying resource (`rtl_power` from the OpenCyber rf toolkit), which distinguishes it from siblings like oc_rtl_433, oc_rtl_sdr, or oc_rtl_test purely by naming the wrapped binary. It stops short of saying what rtl_power actually does (frequency/power sweep), so an agent unfamiliar with the tool still has to infer purpose from the binary name.

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 guidance on when to use this tool instead of the other RTL-SDR family tools, and no prerequisites or exclusion conditions are stated. The only operational guidance is 'use relative paths for engagement artifacts', which is about invocation, not tool selection.

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