Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_wifite

Destructive

Automates authorized wireless audits by wrapping aircrack-ng, reaver, and hashcat; run from the engagement namespace and use relative paths for artifacts.

Instructions

Automated authorized wireless audit wrapper around aircrack-ng, reaver, and hashcat. Prefer explicit per-step tools when evidence quality matters. 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_wifite"
  }
}

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

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, non-idempotent and non-read-only, so safety is largely covered. The description adds meaningful context the annotations do not: the 'authorized' framing implies an authorization prerequisite, and it discloses that execution is scoped to the engagement namespace with relative-path conventions. It does not say what the wrapper actually does to targets (deauth, handshake capture, files written to disk), which would be the highest-value disclosure for a destructive tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler, and the identifying clause comes first. The routing hint and the path/namespace convention follow in a sensible order. Nothing here could be trimmed without losing information.

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 explained, and annotations already carry the risk profile. However, for a destructive, automated wrapper with 0% schema coverage, the definition leaves the agent without the argument-vector convention, any prerequisite such as monitor mode or interface availability, or a sense of what artifacts/side effects are produced. It is workable but under-specified at the invocation level.

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 coverage is 0% across 4 parameters, so the description must carry the burden. It partially explains working_directory/engagement scoping ('use relative paths for engagement artifacts'), but the most important parameter, `arguments` (a raw CLI arg vector for the wrapped tool), and `stdin` receive no guidance at all — no syntax, format, or example. An agent must guess how to construct the invocation, which is a serious gap for a wrapper tool.

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?

Names a specific artifact (an automated wireless audit wrapper) and enumerates the underlying engines it orchestrates (aircrack-ng, reaver, hashcat), which tells the agent this is a bundled/automated step rather than a single primitive. It gestures at the per-step siblings ('explicit per-step tools') without naming them, so the differentiation is real but not crisp.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit when-not rule: 'Prefer explicit per-step tools when evidence quality matters,' which is exactly the kind of routing guidance an agent needs between this wrapper and the granular siblings. It lacks a positive 'use this when you want a full automated sweep' statement and names no specific sibling tool, so it stops short of a complete routing rule.

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