Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_ubertooth_util

Destructive

Control and query an Ubertooth One Bluetooth/BLE radio within an engagement namespace to capture and analyze wireless traffic, using relative paths for engagement artifacts.

Instructions

Query and control an Ubertooth One Bluetooth/BLE radio. 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_util"
  }
}

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
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered structurally. The description is consistent with that ('control' implies mutation) and adds the namespace/relative-path constraint, which is genuinely useful context. It does not disclose that arguments are passed through to the underlying ubertooth-util binary, nor what state changes or hardware side effects to expect beyond what annotations say.

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 short sentences, front-loaded with the resource, with no filler or repetition. The brevity is efficient rather than padded, though it is arguably too terse for a destructive raw-argument wrapper.

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?

The tool takes an unconstrained string array passed to a radio control utility, is flagged destructive and non-idempotent, and has zero schema descriptions; the description should explain the argument contract and hardware effects. An output schema exists, so return values need not be covered. As written, an agent has enough to know what the tool touches but not enough to call it safely or 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 all four parameters, so the description must carry the burden and largely does not. The only parameter-relevant hint is 'use relative paths', which loosely maps to working_directory; engagement_id, stdin, and especially the free-form 'arguments' string array are completely unexplained. An agent has no way to know what CLI flags or subcommands belong in 'arguments'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (Ubertooth One Bluetooth/BLE radio) and a verb pair ('query and control'), which is better than a bare restatement. But 'query and control' is broad enough to cover almost any operation, and it gives no signal distinguishing it from siblings such as oc_ubertooth_rx or oc_ubertooth_scan. An agent cannot tell which ubertooth entry point to pick from this text alone.

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 scoping ('runs from the selected engagement namespace', 'use relative paths'), with no statement of when this tool is the right choice versus the rx/scan siblings. There are no prerequisites, exclusions, or conditions given. This is invocation hygiene, not usage 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