Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_one_gadget

Destructive

Executes one_gadget with supplied arguments to identify one-shot exploitation gadgets in binary artifacts within an engagement workspace, without shell parsing.

Instructions

Run one gadget from the OpenCyber binary toolkit. The container executes one_gadget 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_one_gadget"
  }
}

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.6/5.0
Behavior4/5

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

The annotations already declare destructive=true, readOnly=false, idempotent=false, and openWorld=false, so the safety profile is covered. The description adds useful execution context beyond annotations: the container executes the binary directly with argv tokens, shell parsing is never used, and execution occurs from the selected engagement namespace. It does not describe permissions or side effects in detail, but that is less necessary given the destructive annotation.

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 front-loaded and efficient, with three short sentences that convey execution mode and path context. There is slight redundancy between 'Run one gadget' and 'executes `one_gadget` directly', but no unnecessary wording.

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 annotations cover the destructive safety profile. The description adequately explains the execution model and namespace-relative paths, but with four parameters at 0% schema description coverage it leaves `stdin` and some parameter semantics underdocumented.

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

Parameters3/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 carry parameter meaning. It clarifies that `arguments` are argv tokens passed directly without shell parsing and that relative paths apply within the engagement namespace, which helps for `arguments`, `working_directory`, and `engagement_id`. However, `stdin` is not mentioned and `engagement_id` is only indirectly explained, leaving clear gaps.

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 verb and resource: run the `one_gadget` binary from the OpenCyber toolkit. It also clarifies that execution is direct via argv rather than through a shell, which helps distinguish it from a generic shell tool. It does not explicitly explain what `one_gadget` is for or name alternatives, so it falls short of full sibling differentiation.

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?

Usage is implied by the purpose: use this tool when running the `one_gadget` binary. The description adds operational guidance about relative paths in the engagement namespace, but it gives no explicit when-to-use versus when-not-to-use guidance and does not name alternatives such as a generic shell tool.

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