Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hcxpcapngtool

Destructive

Convert hcxdumptool/hcxtools packet captures into hashcat-compatible material within an engagement namespace; use relative paths for engagement artifacts.

Instructions

Convert hcxdumptool/hcxtools captures into hashcat-compatible material. 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_hcxpcapngtool"
  }
}

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, idempotentHint=false, readOnlyHint=false and openWorldHint=true, so the safety profile is covered in structured data. The description adds the namespace and relative-path constraint, which is useful, but does not say what files are created or overwritten, or that the arguments are passed straight to the underlying 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 tight sentences with the purpose front-loaded and no wasted wording. Brevity is appropriate, though the second sentence could carry more operative detail about argument passing at no extra length cost.

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, but for a destructive, non-idempotent tool with an undocumented required `arguments` array and stdin, the description leaves real gaps in how to invoke it 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 four parameters, so the description must compensate and largely does not. It alludes to engagement_id and working_directory via the namespace/relative-path sentence, but says nothing about the required `arguments` array (the CLI passthrough, the key input) or the optional `stdin` parameter.

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 (convert) with a clear resource (hcxdumptool/hcxtools captures) and the produced artifact type (hashcat-compatible material). This distinguishes it well from aircrack/airodump siblings, though it does not explicitly name a preferred 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?

Gives operating context (runs from the selected engagement namespace, use relative paths for engagement artifacts) but offers no when-to-use/when-not guidance or comparison to related cracking tools. The usage context is implied rather than prescribed.

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