Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_ubertooth_rx

Destructive

Receive and follow Bluetooth Low Energy connections with an Ubertooth One inside an engagement namespace, using relative paths for artifacts.

Instructions

Receive and follow Bluetooth Low Energy connections 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_rx"
  }
}

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.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is carried by structured data. The description adds hardware and namespace context but never says what is destructive, whether traffic is written to disk in the engagement, how long it runs, or how to stop it — gaps that matter for a destructive, non-idempotent tool.

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 sentences, front-loaded with the action and resource, with no wasted wording. It is efficiently written, though the brevity edges toward under-specification rather than genuine conciseness.

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 need not be described, but the rest is thin for a destructive tool with four undocumented parameters. An agent still cannot tell what 'arguments' should contain, what the hardware requirements are, or what side effects to expect in the engagement directory.

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 four parameters, so the description must compensate and largely does not. The only hint is 'use relative paths for engagement artifacts,' which loosely touches working_directory; nothing explains that 'arguments' is a raw CLI argument vector, what 'stdin' is for, or what engagement_id must reference.

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+resource: 'Receive and follow Bluetooth Low Energy connections with an Ubertooth One.' That distinguishes it in practice from a scan tool, but it never names or contrasts a sibling such as oc_ubertooth_scan, so the differentiation is implicit rather than stated.

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?

Implies the use case (following an established BLE connection rather than scanning) and gives scoping guidance about the engagement namespace and relative paths. It offers no explicit when-not-to-use, no prerequisites like adapter availability, and no named alternative for discovery.

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