Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_unblob

Destructive

Extract and recursively unpack firmware images with unblob, using relative paths inside the selected engagement namespace for contained artifact analysis.

Instructions

Extract and recursively unpack firmware images with unblob. 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_unblob"
  }
}

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

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

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false, and non-idempotent, so the risk profile is known. The description adds genuinely new behavioral context — the execution namespace and path-resolution rule — but says nothing about where output lands, whether existing directories are overwritten, or expected runtime on large images, which matters for a destructive extraction 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 short sentences with the core action front-loaded and the operational constraint second. Nothing is padded, though the second sentence is compressed to the point of ambiguity about what 'relative paths' applies to.

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?

An output schema exists, so return values need not be described. However, for a tool whose primary input is an unconstrained string array of CLI arguments, the absence of any guidance on accepted flags, target path placement, or output location leaves an agent guessing at invocation — a substantial gap for a destructive, open-world operation.

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 only hints at working_directory/engagement_id semantics via 'relative paths' and 'engagement namespace'; the two most important inputs, `arguments` (an array of raw unblob CLI flags) and `stdin`, receive no explanation at all.

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 gives a specific verb pair and resource: 'Extract and recursively unpack firmware images with unblob.' An agent knows exactly what operation is performed. It does not distinguish itself from the closely related sibling oc_binwalk, which is a comparable carving/extraction tool, so it stops short of a 5.

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 rather than stated: it runs 'from the selected engagement namespace' and expects 'relative paths for engagement artifacts,' which tells the agent how to invoke it in context. There is no explicit when-to-use versus when-not, and no mention of the obvious alternative (oc_binwalk) or of preconditions such as a downloaded artifact already existing.

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