Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_qemu_arm

Destructive

Emulate a single ARM user-space binary to run firmware that cannot execute directly in the container; use engagement-relative paths for artifacts.

Instructions

Emulate a single ARM user-space binary. Useful for firmware binaries that cannot run in the container directly. 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_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.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotent, so the risk profile is covered. The description adds that execution happens from the selected engagement namespace and that artifact paths are relative, which is genuinely useful context. It says nothing about execution timeout, exit-code/failure behavior, or that untrusted binaries are being run, leaving real behavioral gaps.

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, then the use case, then the path constraint. No redundant wording, though the namespace/path sentence could be tightened.

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 not be explained, and annotations cover the safety profile. However, for a destructive arbitrary-binary execution tool with zero parameter documentation, the description should mention how arguments/stdin are wired and what a failed or timed-out run looks like.

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%, so the description carries the full burden. It clarifies working_directory ('use relative paths for engagement artifacts') and implies engagement_id via 'selected engagement namespace', but says nothing about how 'arguments' are passed or what 'stdin' accepts, leaving two 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?

States a specific verb and resource: 'Emulate a single ARM user-space binary.' The qualifier 'user-space' implicitly distinguishes it from the sibling system-emulation tool, so an agent can reasonably tell them apart, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Useful for firmware binaries that cannot run in the container directly' gives a clear condition that selects this tool over plain shell execution. It stops short of naming an alternative or stating when-not to use it, so it falls short of a 5.

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