Skip to main content
Glama

firmware_scan

Scan firmware images or packed binaries to detect embedded files, filesystems, and UPX packing, helping identify unpacking and extraction targets.

Instructions

Scan a firmware image or packed binary for embedded files/filesystems (binwalk) and UPX packing.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it delivers little: it discloses the underlying engines (binwalk, UPX) but not whether the operation is read-only, whether it extracts files or only reports them, expected runtime, or permission needs. The verb 'scan' implies non-destructive behavior but that is inference, not disclosure.

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?

A single dense sentence with the action front-loaded and the detection targets following, with no filler. The parenthetical engine name (binwalk) is compact and informative rather than padding.

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?

With no annotations and no output schema, the description must stand in for both, yet it says nothing about what a scan returns (a list of detected offsets? extracted artifacts?) or how long it may take. For a scanning tool whose result shape is undefined elsewhere, that is a meaningful gap.

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% and the single required parameter 'path' is never explained. The description implies the path points to a firmware image or packed binary, but leaves open whether it is a local absolute path, a mounted volume path, or a URL, and adds no format or constraint details.

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?

Names a specific verb (scan) plus the resource class (firmware image or packed binary) and enumerates what is detected: embedded files/filesystems via binwalk and UPX packing. That specificity implicitly separates it from siblings like extract_strings or triage_binary, though no sibling is named to make the boundary explicit.

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?

There is no explicit when-to-use or when-not-to-use statement and no prerequisites. Guidance is only implied by the input scoping (a firmware image or packed binary), which tells the agent what to point it at but not how it compares to triage_binary or extract_strings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.