Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_firmware_analyze

Destructive

Triage firmware images by extracting cryptographic hashes, architecture identity, entropy maps, strings, and binwalk signatures, then persist a JSON report without executing the image.

Instructions

Triage a firmware image inside the engagement: cryptographic hashes, magic/architecture identity, entropy map, interesting strings, binwalk signatures, review items, and a persisted JSON report. Never executes the image.

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>",
      "path": "<path>"
    },
    "name": "oc_firmware_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
run_binwalkNo
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations declare readOnlyHint=false and destructiveHint=true, and the description usefully explains why: a JSON report is persisted. It also adds a strong behavioral guarantee not in the annotations ("Never executes the image"), which reassures an agent the target binary is not run. It does not disclose where the report lands or whether it overwrites prior output, so it stops short of full transparency.

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?

A single dense sentence, front-loaded with the action and scope, followed by the produced artifacts and the non-execution caveat. No filler and nothing redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 spelled out, and the description still summarizes them helpfully. Given a disruptive (destructiveHint=true) three-parameter tool, the main remaining gaps are report persistence location, overwrite behavior, and guidance against the lower-level binwalk sibling.

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 the burden. It conveys the gist of 'path' (the firmware image) and 'engagement_id' (scoping), and "binwalk signatures" hints that run_binwalk controls that stage, but it never states that mapping explicitly, nor default behavior, accepted path forms, or size limits.

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 ("Triage") and resource ("a firmware image inside the engagement") and enumerates the concrete artifacts produced: hashes, magic/architecture identity, entropy map, strings, binwalk signatures, review items, and a JSON report. That is far more informative than the bare name, though it never contrasts itself with sibling analyzers such as oc_binwalk or oc_angr_analyze, leaving the differentiation to inference.

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?

"Inside the engagement" implies the engagement_id requirement and static-only use, and "Never executes the image" signals a safe inspection step in a triage workflow. However, there is no explicit when-to-use versus when-to-pick-oc_binwalk guidance, no prerequisite state, and no exclusions.

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