Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_apktool

Destructive

Decode, rebuild, and inspect Android APK resources and smali code to analyze app structure and reverse-engineer packages. Runs inside an isolated engagement workspace.

Instructions

Decode, rebuild, and inspect Android APK resources and smali. 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_apktool"
  }
}

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

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the agent knows this writes and reaches outside. The description adds no compensating detail beyond that: it never says that decode/rebuild creates output directories on disk, whether existing artifacts are overwritten, or what permissions are needed, even though 'rebuild' implies mutation of engagement state.

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, front-loaded with the capability statement followed by the environment constraint, with no filler. It is efficient, though its brevity is also the source of the gaps elsewhere.

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 taking a raw argument vector plus stdin and working directory, the description omits the things an agent most needs: how 'arguments' is structured, that output is written to disk in the working directory, and how stdin is consumed. The presence of an output schema excuses it from documenting return values, but nothing else compensates for the 0% parameter coverage.

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% for all four parameters, so the description carries the full burden and largely fails it. The mention of engagement namespace and relative paths loosely gestures at engagement_id and working_directory, but the critical 'arguments' argv array and 'stdin' passthrough are never explained, nor is the expected argument format for apktool flags.

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 opens with three specific verbs (decode, rebuild, inspect) applied to a concrete resource (Android APK resources and smali), which is far more informative than the bare name 'oc_apktool'. It does not, however, distinguish itself from adjacent binary/forensics tools such as oc_binwalk, leaving the agent to infer that this one is Android-specific.

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 sentence 'Runs from the selected engagement namespace; use relative paths for engagement artifacts' gives operational context about where files resolve, which implicitly defines the usage setting. There is no explicit when-to-use/when-not guidance or named alternative, so selection between this and other analysis tools is left to inference.

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