Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_jadx

Destructive

Decompile Android DEX/APK bytecode for mobile application review and inspect engagement-scoped app artifacts using relative paths.

Instructions

Decompile Android DEX/APK bytecode for mobile application review. 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_jadx"
  }
}

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 description should add the details annotations can't carry: where decompiled output lands, whether existing files are overwritten, and expected runtime on large APKs. It offers none of that, only a note that execution is scoped to the engagement namespace.

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 tight sentences with the purpose front-loaded and the operational constraint second. Nothing is wasted, though brevity here comes partly at the cost of the missing parameter guidance.

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?

This is a complex, destructive, open-world CLI-wrapper with a required free-form arguments array and an output schema. The description explains neither the arguments passthrough nor the on-disk side effects, so an agent cannot confidently invoke it beyond a trivial case.

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 four parameters, so the description must compensate. It partially covers working_directory/engagement scoping via 'runs from the selected engagement namespace; use relative paths', but the 'arguments' array (clearly a jadx CLI passthrough) and 'stdin' are left entirely unexplained, which is the most consequential gap for correct invocation.

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 and resource: decompile Android DEX/APK bytecode for mobile application review. That is clearly distinguishable from generic tooling, though it never distinguishes itself from the closely related sibling oc_apktool, which an agent would likely weigh against it.

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?

Usage is only implied by 'for mobile application review', plus one concrete operational rule about relative paths and the engagement namespace. There is no statement of when to choose this over oc_apktool or other Android analysis tools, and no preconditions such as requiring the APK to be staged in the engagement.

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