Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_bladerf

Destructive

Control and query a Nuand bladeRF SDR through bladeRF-cli from the selected engagement namespace, using relative artifact paths.

Instructions

Control and query a Nuand bladeRF SDR through the bladeRF-cli. 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_bladerf"
  }
}

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 already flag destructiveHint=true and openWorldHint=true, so the safety profile is declared; the description adds only the working-directory/namespace behavior. It does not warn that arbitrary CLI arguments can reconfigure or brick a radio, nor mention permission or device-state requirements, which is the key risk context for a raw CLI passthrough.

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 tight, front-loaded sentences with no filler. It is concise, but the brevity is achieved by omitting the invocation semantics rather than by efficient editing.

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 raw-CLI passthrough tool with zero parameter documentation, the definition should explain how arguments map to bladeRF-cli syntax and what stdin is for. An output schema exists, so return values need not be described, but the invocation contract is missing.

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 compensate and largely does not. 'Runs from the selected engagement namespace' and 'use relative paths' loosely gesture at engagement_id and working_directory, but the required `arguments` array and optional `stdin` — the core of how this tool is invoked — are never explained.

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+resource: control and query a Nuand bladeRF SDR via bladeRF-cli. That is concrete and distinguishes it from the RF-adjacent siblings, though it does not explicitly contrast with any named alternative.

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?

Gives operational context (runs in the engagement namespace, use relative paths for artifacts) but never says when to choose this tool over another, what preconditions exist (device attached, permissions, CLI availability), or when it should not be used.

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