Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_soapy_sdr

Destructive

Query and probe SDR hardware through the SoapySDR abstraction layer from an engagement namespace, using relative paths for engagement artifacts.

Instructions

Query and probe SDR hardware through the SoapySDR abstraction layer. 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_soapy_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.7/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, but the description only says "query and probe" and does not disclose destructive risk, hardware access implications, or permission requirements. The namespace/path note adds some operational context, but the behavioral profile is largely left to annotations.

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?

The description is two sentences and front-loads the core purpose before the namespace/path note. It is efficient, though the second sentence is operational rather than explanatory.

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?

For a destructive, open-world SDR tool with four parameters and no schema descriptions, the definition is too thin. The output schema exists, so return values need not be described, but the description should do more to explain arguments, stdin, and destructive behavior.

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. The description clarifies the engagement namespace and relative-path expectation, which loosely maps to engagement_id and working_directory, but it leaves the required arguments array and optional stdin completely unexplained.

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 states a specific verb and resource: "Query and probe SDR hardware" through the SoapySDR abstraction layer. This distinguishes it from vendor-specific siblings like oc_rtl_sdr and oc_bladerf, though it does not explicitly route between 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?

The only usage context is that it runs from the selected engagement namespace and should use relative paths for engagement artifacts. There is no guidance on when to choose this tool over vendor-specific SDR tools or other probing tools.

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