Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_bluetoothctl

Destructive

Executes bluetoothctl commands for Bluetooth device discovery and control within an isolated engagement workspace, passing argv tokens directly without shell parsing for authorized wireless testing.

Instructions

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

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

A3.8/5.0
Behavior4/5

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

Annotations already declare destructive, non-idempotent, open-world behavior, so the description only needs to add execution semantics — and it does: no shell parsing, argv tokens passed straight to bluetoothctl, and scoped to the engagement namespace. It does not describe what state may be altered or any privilege requirements, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose, then the execution model, then the path/namespace rule. No filler and nothing repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 described, and the description covers the critical execution model and path scoping for a wrapper tool. The remaining gap is guidance on choosing this over the general-purpose shell sibling, which matters for a destructive open-world tool.

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. It explains that `arguments` are raw argv tokens (no shell interpretation) and hints at engagement scoping and relative working directories, but `stdin` is never mentioned and no format/syntax guidance is given for argv or paths.

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 and resource: run `bluetoothctl` from the OpenCyber wireless toolkit. The argv-token execution model is spelled out, which makes it clearly distinct from a generic shell runner. It stops short of explicitly naming the sibling it should be preferred over (e.g. oc_bash).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is only implied: you use it when you want bluetoothctl, run against a selected engagement namespace with relative paths for artifacts. There is no explicit when-to-use/when-not statement and no named alternative for raw command execution.

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