Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_ubertooth_scan

Destructive

Discover classic Bluetooth and BLE devices with an Ubertooth One from an engagement namespace, capturing scan artifacts for wireless reconnaissance.

Instructions

Discover classic Bluetooth and BLE devices with an Ubertooth One. 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_ubertooth_scan"
  }
}

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 declare destructiveHint=true, openWorldHint=true, and non-idempotent, but the description adds nothing about what could be destroyed, what hardware state is required, how long a scan runs, or whether results stream or return at completion. With destructive=true, an agent needs more than "discover" to act safely.

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 sentences, front-loaded with the core action and followed by the scoping constraint. No wasted wording, though the second sentence is cryptic about which parameter it maps to.

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?

An output schema exists so return values needn't be described, but for a hardware-dependent, destructive, open-world scan with a raw passthrough `arguments` array, the definition leaves the agent without the operational details needed to invoke it correctly.

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 4 parameters. The description only alludes to working_directory ("use relative paths") and engagement_id ("selected engagement namespace"); the required `arguments` array and `stdin` are completely unexplained, so the agent cannot tell how to pass Ubertooth CLI flags.

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 gives a specific verb and resource: "Discover classic Bluetooth and BLE devices with an Ubertooth One." That distinguishes it reasonably from receive-oriented siblings like oc_ubertooth_rx, though it never names an alternative explicitly.

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 choose this scan over oc_ubertooth_rx, oc_bluetoothctl, or the other scanning tools, and no stated prerequisites such as requiring an attached Ubertooth One. Only the namespace/path convention is mentioned.

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