Skip to main content
Glama
MarwanDevSpace

mcp-flutter-apk-injector

Decode Android APK into workspace

decompile_apk
Destructive

Decode an APK into a readable workspace of Smali code, resources, assets, and manifest for later analysis or modification.

Instructions

Decode an APK into a Smali, resources, assets, native-library, and manifest workspace for later analysis or modification. The input APK is read-only, but outputDir is removed and recreated; use analyze_injection_surface next, and do not call this when a valid decoded workspace already exists. Full source decoding requires apktool and Java, while decompileSources=false is limited to resource and manifest inspection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apkPathYesAbsolute path to target source .apk file to decompile
outputDirYesDestination directory path where decompiled Smali code, resources, assets, and AndroidManifest.xml will be extracted
decompileSourcesNoWhether to disassemble DEX files into Smali code (default: true). Set false for resource/asset-only disassembly

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileCountYesNumber of extracted workspace files.
smaliRootYesPrimary Smali root, when source decoding was enabled.
sourceApkYesAbsolute path to the input APK that was read.
targetAbisYesNative ABI directories detected in the workspace.
packageNameYesPackage name parsed from AndroidManifest.xml.
mainActivityYesResolved launcher activity, when present.
manifestPathYesAbsolute path to decoded AndroidManifest.xml.
workspaceDirYesAbsolute path to the decoded workspace.
hasNativeLibsYesWhether the decoded workspace contains native libraries.
minSdkVersionYesDeclared minimum Android API level.
applicationClassYesDeclared application class, when present.
targetSdkVersionYesDeclared target Android API level.
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses that outputDir is removed and recreated, and that the input APK is read-only. It also mentions the apktool and Java prerequisite, adding meaningful context not present in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose, and each sentence adds new information (purpose, behavior, prerequisites). No redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage boundaries, dependencies, destructive behavior, and pipeline guidance. Combined with the output schema, it is fully sufficient for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; description adds specific semantics for outputDir (removed/recreated) and decompileSources (limited to resource and manifest inspection when false). This extra context helps the agent understand parameter side effects beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool decodes an APK into a named workspace with specific components (Smali, resources, assets, native-library, manifest) for later analysis or modification. This distinguishes it from sibling tools like analyze_injection_surface, which operate on an already-decoded workspace.

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

Usage Guidelines5/5

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

Explicitly states to use analyze_injection_surface next, and advises against calling when a valid decoded workspace already exists. It also differentiates between full source decoding and resource/asset-only mode, providing clear usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MarwanDevSpace/mcp-flutter-apk-injector'

If you have feedback or need assistance with the MCP directory API, please join our Discord server