Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_btmgmt

Destructive

Run btmgmt Bluetooth management commands with direct argv tokens and no shell parsing inside an engagement workspace for authorized wireless testing.

Instructions

Run btmgmt from the OpenCyber wireless attack toolkit. The container executes btmgmt 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_btmgmt"
  }
}

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.4/5.0
Behavior4/5

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

Annotations already declare destructive=true, openWorld=true, and non-idempotent, so the safety profile is covered. The description adds genuinely new behavioral context: argv tokens are executed directly with no shell parsing, and execution is scoped to the selected engagement namespace — both material facts for how the command will behave. It stops short of describing output or timeouts, but the added execution-semantics detail is real value.

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 short sentences, front-loaded with what the tool does, followed by execution semantics and path conventions. No filler or repetition, though the sentences are somewhat clipped and could be organized with clearer separation between invocation mechanics and path rules.

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 not be explained, and annotations cover the destructive/open-world profile. Still missing for a destructive CLI wrapper are sibling differentiation from oc_bluetoothctl and any coverage of the 'stdin' parameter, leaving the definition adequate but with clear gaps.

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?

With 0% schema description coverage, the description must carry parameter meaning, and it does explain that 'arguments' is a raw argv token list with no shell interpretation, plus that 'working_directory' is relative to the engagement namespace selected by 'engagement_id'. However, the 'stdin' parameter is never mentioned, so the compensation is incomplete.

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 names a specific verb ('Run') and a specific resource ('btmgmt'), and places it in the OpenCyber wireless attack toolkit so the agent knows it is a wrapper around the Bluetooth management CLI. It does not distinguish this from the closely related sibling oc_bluetoothctl, so an agent must infer which Bluetooth tool to pick.

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 btmgmt versus alternatives such as oc_bluetoothctl, nor any stated prerequisites or exclusions. The only directive is a working-directory convention ('use relative paths for engagement artifacts'), which is operational rather than tool-selection guidance.

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