Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_xxd

Destructive

Executes xxd directly with supplied argv tokens to inspect or convert binary data in an isolated engagement namespace; use relative paths for engagement artifacts.

Instructions

Run xxd from the OpenCyber binary toolkit. The container executes xxd 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_xxd"
  }
}

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 and readOnlyHint=false, so the safety profile is covered structurally. The description adds genuinely useful context the annotations do not: no shell parsing occurs, execution is scoped to the selected engagement namespace, and paths are engagement-relative. It does not, however, explain what makes the operation destructive (e.g. that xxd can write output files) or how stdin is consumed, which is the main behavioral gap.

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, front-loaded with the core action and followed by execution-semantics and path constraints. No filler or redundancy; it could only be improved by spending a clause on stdin rather than adding length.

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 no explanation, and the safety profile is in annotations. What remains missing is the tool's actual capability (what xxd does and that it can emit or reverse hex dumps) and how `stdin` is fed, which matters for a general-purpose binary wrapper with four parameters.

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 and it partially does: 'supplied argv tokens' clarifies `arguments`, 'engagement namespace' clarifies `engagement_id`, and 'relative paths' implies `working_directory`. The `stdin` parameter — arguably the most consequential for a shell-free binary wrapper — is never mentioned, leaving one of four parameters undocumented anywhere.

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: it runs the `xxd` binary from the OpenCyber toolkit, with argv tokens passed directly. That is clearly distinguishable from siblings like oc_bash or oc_binwalk in mechanism, though it never explains what xxd itself does (hex dump / reverse-hexdump), so an agent unfamiliar with the binary must infer capability from the name alone.

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?

There is no when-to-use or when-not-to-use guidance and no alternative tool is named, despite many overlapping siblings. The only directive is a path convention ('use relative paths for engagement artifacts'), which is a constraint on invocation rather than guidance on tool selection.

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