Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_iwconfig

Destructive

Configure and inspect legacy wireless interfaces within a selected engagement namespace, using relative paths for engagement artifacts.

Instructions

Legacy wireless interface configuration and status. 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_iwconfig"
  }
}

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
Behavior3/5

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

The annotations already disclose that this is a destructive, non-read-only, open-world operation. The description adds some useful context about running in the engagement namespace and relative paths, but it does not explain destructive implications, required permissions, or what kind of changes can be made.

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?

The description is two short sentences with no wasted wording, and it front-loads the primary purpose before adding operational context. It could be improved with a little more structure around usage and parameters, but it is appropriately concise.

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?

For a destructive command wrapper that accepts an arbitrary arguments array, the definition leaves critical invocation details unspecified. Although an output schema and safety-related annotations exist, the description still does not give an agent enough information to call the tool correctly or understand the argument format.

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%, so the description must compensate for all four parameters. It only partially clarifies engagement_id and working_directory via the namespace and relative-path note; the key arguments array and stdin parameter are left completely 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 states a specific resource and function: wireless interface configuration and status. It is clear that this wraps legacy iwconfig behavior, though it does not distinguish the tool from other wireless-related siblings.

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 offers no explicit when-to-use guidance or comparison with alternatives. It only notes that it runs from the selected engagement namespace and to use relative paths, which is operational context rather than tool selection guidance.

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