Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_qemu_system_arm

Destructive

Emulate a full ARM system to analyze firmware and embedded targets, running inside an engagement namespace and using relative paths for engagement artifacts.

Instructions

Emulate a full ARM system for firmware and embedded target analysis. 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_qemu_system_arm"
  }
}

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 and openWorldHint=true, so the safety profile is covered. The description adds genuinely new context — execution is scoped to the engagement namespace and artifact paths are relative — but it never warns that arbitrary emulator arguments produce side effects, nor describes how output is captured.

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 sentences, front-loaded with the action and followed by the operational constraint; no filler. It is efficient but so terse that the second sentence is doing almost all the parameter-adjacent work.

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?

For a destructive, open-world tool with 0% schema coverage and four parameters, the description omits how to construct the arguments array, what stdin is for, and what the output schema returns in practice. The presence of an output schema excuses return-value detail, but not the missing invocation semantics.

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 coverage is 0%, so the description must carry the parameter burden, and it largely fails. It never explains that 'arguments' is a raw QEMU command-line argument list, or what 'stdin' supplies; only 'use relative paths' indirectly hints at working_directory.

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?

States a specific verb and resource: 'Emulate a full ARM system', plus the domain ('firmware and embedded target analysis'). It does not explicitly distinguish itself from the near-identical sibling oc_qemu_arm, so the agent cannot tell which emulation tool to pick from the description alone.

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?

The phrase 'for firmware and embedded target analysis' implies a usage context, and 'Runs from the selected engagement namespace' gives an operating precondition. However, there is no explicit when-to-use vs. when-not guidance and no named alternative such as oc_qemu_arm.

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