Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_rtl_sdr

Destructive

Capture raw IQ samples from a Realtek RTL-SDR dongle into an engagement artifact, using relative paths within the selected engagement namespace.

Instructions

Capture raw IQ samples from a Realtek RTL-SDR dongle into an engagement artifact. 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_sdr"
  }
}

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 non-idempotent behavior, so the safety profile is covered. The description adds that output lands in an engagement artifact and that paths are relative to the engagement namespace, but it omits what happens if the dongle is already in use, whether a prior artifact is overwritten, or what hardware/permission prerequisites exist.

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 the action and resource, with no filler. The size is appropriate for the tool, though the second sentence spends space on path conventions while leaving the arguments array unaddressed.

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 explanation. However, for a hardware capture tool with four parameters including an opaque passthrough argument vector, the description leaves the agent without enough information to invoke it correctly, which is a substantial completeness gap.

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 coverage is 0%, so the description must compensate and largely does not. It hints that working_directory should be relative and that engagement_id selects the namespace, but the most important parameter — the 'arguments' array, presumably raw rtl_sdr CLI flags for frequency, sample rate, and duration — is completely unexplained, leaving the agent unable to construct a valid call.

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 pairs a specific verb ('Capture raw IQ samples') with a specific resource ('Realtek RTL-SDR dongle') and states the output destination ('engagement artifact'). It implicitly differentiates from generic SDR siblings like oc_soapy_sdr by naming the RTL-SDR hardware, though it never explicitly contrasts them.

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?

It tells the agent the operating context ('runs from the selected engagement namespace', 'use relative paths'), which is invocation guidance, but it gives no when-to-use or when-not-to-use direction relative to oc_soapy_sdr, oc_rtl_power, or oc_rtl_test. An agent cannot tell from this text which SDR capture tool to select.

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