Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_airodump

Destructive

Run airodump-ng with explicit argv tokens in an engagement namespace to capture wireless traffic and save artifacts via relative paths.

Instructions

Run airodump from the OpenCyber wireless toolkit. The container executes airodump-ng 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_airodump"
  }
}

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.4/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 non-idempotent, so the risk profile is known; the description adds a genuinely useful execution detail (argv passed directly with no shell parsing) and the engagement-namespace scoping with relative-path convention. However, it never says what airodump actually writes to disk or where capture artifacts land, which is the most important behavioral fact for a destructive, open-world 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?

Three short sentences, front-loaded with the verb and binary, with no filler or repetition. The third sentence is somewhat compressed ("selected engagement namespace") but still carries actionable information about path handling.

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 annotations cover the safety profile; what remains is execution semantics, which the description handles well. The only real gap is the undocumented `stdin` parameter and the absence of any mention of what the tool produces or where captures are written.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 the load, and it does for most parameters: `arguments` is clarified as raw argv tokens passed without shell parsing, `engagement_id` as the namespace the run is scoped to, and `working_directory` as the base for relative artifact paths. Only `stdin` goes unexplained.

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 names a specific verb and resource ("Run airodump", "executes airodump-ng directly") and pins down the exact binary, so the agent knows this is a thin argv wrapper rather than a higher-level wireless workflow. It does not differentiate from nearby siblings such as oc_airmon or oc_aireplay, leaving the agent to infer the boundary from the tool name 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 description explains how to invoke the tool (argv tokens, no shell parsing, relative paths) but never states when to choose airodump over sibling wireless tools or what prerequisites exist. There is no when-not-to-use guidance or named alternative, so selection still depends on the agent's prior knowledge of airodump-ng.

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