Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hcxdumptool

Destructive

Capture Wi-Fi management frames and PMKID/EAPOL data for authorized wireless assessments. Require monitor-mode hardware and run from the engagement namespace using relative artifact paths.

Instructions

Capture Wi-Fi management frames and PMKID/EAPOL material for authorized wireless assessments. Requires monitor-mode capable hardware. 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_hcxdumptool"
  }
}

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.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely new operational context — monitor-mode hardware requirement and engagement-namespace/relative-path behavior — but omits how the tool behaves in practice (whether it runs until interrupted, whether it writes capture files, what the `arguments` array is passed to).

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, each carrying distinct information (what it captures, hardware prerequisite, execution context), with the core purpose front-loaded. No filler or repetition.

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 the hardware prerequisite is a good addition. Still, for a raw-argument CLI wrapper with no documented parameters, the definition should explain what `arguments` accepts (hcxdumptool flags) and what `stdin` is for; without that, an agent can construct a call but not a correct one.

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 carry the load. The sentence about the engagement namespace and relative paths partially explains engagement_id and working_directory, but the two most important parameters — `arguments` (raw CLI arguments) and `stdin` — are never mentioned at all, leaving an agent to guess their format.

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 uses a specific verb and resource: 'Capture Wi-Fi management frames and PMKID/EAPOL material'. That is far more informative than the tool name alone and implicitly separates it from cracking siblings like oc_aircrack, though it does not name a specific alternative.

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?

It states a precondition ('Requires monitor-mode capable hardware') and frames the use case as 'authorized wireless assessments', which is useful context. However, it never says when to pick this over sibling tools such as oc_airodump or oc_airmon, nor does it say what conditions make it the wrong choice.

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