Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_btmon

Destructive

Executes Bluetooth monitoring commands with direct argument tokens and no shell parsing inside an engagement namespace for authorized wireless analysis.

Instructions

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

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/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 idempotentHint=false, so the safety profile is supplied. The description's genuinely useful addition is the no-shell-parsing execution model, which tells the agent not to rely on quoting or pipes; however, it never says what could be destroyed, what privileges are needed, or how long the command runs, so it adds only modest context beyond 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?

Three short sentences, front-loaded with what runs and how, then the namespace/path rule. No filler, though the path sentence could be folded into a single clause without loss.

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 described, and annotations cover the risk profile. Still, for a destructive open-world tool with zero schema descriptions, the missing explanation of engagement_id and stdin leaves an agent without enough to construct a correct call confidently.

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%, so the description must carry the burden, and it only partly does. It explains `arguments` (raw argv tokens, no shell parsing) and implies the base for `working_directory` via the engagement namespace, but says nothing about the required `engagement_id` (where to obtain it, what namespace scoping means) or `stdin`.

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 `btmon` from the OpenCyber wireless attack toolkit, executed directly with argv tokens. It is clear what the tool does, but it does not distinguish itself from closely related siblings such as oc_bluetoothctl or oc_airmon, leaving the agent to infer which wireless 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?

The only guidance is operational ('use relative paths for engagement artifacts'), not selection guidance. There is no statement of when to reach for btmon versus other Bluetooth/wireless siblings, nor any precondition such as needing an adapter in monitor mode or an existing engagement.

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