Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_zsteg

Destructive

Detect steganographic content in PNG and BMP files by running zsteg with explicit arguments inside an isolated engagement workspace.

Instructions

Run zsteg from the OpenCyber forensics toolkit. The container executes zsteg 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_zsteg"
  }
}

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

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

Beyond the annotations, the description adds useful execution behavior: the container invokes zsteg directly with argv tokens and never uses shell parsing, and it runs from the engagement namespace. However, despite destructiveHint=true, it does not explain what may be modified or destroyed, nor does it cover permissions or rate limits.

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?

The description is three short, front-loaded sentences with no wasted wording. The command-invocation and path constraints are stated efficiently.

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?

The output schema and annotations carry much of the safety and return-value burden, and the description covers invocation mechanics and path context. Still, for a destructive four-parameter tool with 0% schema coverage, it leaves the stdin parameter and the practical implications of destructive execution insufficiently explained.

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 compensate. It clarifies that 'arguments' are raw argv tokens with no shell parsing and implies working-directory/path behavior, but it does not explain the 'stdin' parameter or give meaningful detail about 'engagement_id'.

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 zsteg from the OpenCyber forensics toolkit.' It makes the execution wrapper nature clear, but does not explain what zsteg itself does or distinguish this wrapper from other forensic tool wrappers.

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 gives operational context about the engagement namespace and relative paths, but it provides no guidance on when to use this tool, when not to use it, or which sibling tools are alternatives.

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