Skip to main content
Glama
zinja-coder

Apktool MCP Server

by zinja-coder
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

decode_apk

Decode Android APK files for reverse engineering analysis with support for selective resource or source decoding and custom output options.

Instructions

Decode an APK file using APKTool with comprehensive validation and error handling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoForce delete destination directory if it exists
no_resNoDo not decode resources
no_srcNoDo not decode sources
timeoutNoCommand timeout in seconds
apk_pathYesPath to the APK file to decode
output_dirNoCustom output directory (optional)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed16 schema fields changedv1.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / apk_path / description
      Added value: +"Path to the APK file to decode"
    • removedInput schema / properties / apk_path / title
      Removed value: -"Apk Path"
    • addedInput schema / properties / force / description
      Added value: +"Force delete destination directory if it exists"
    • removedInput schema / properties / force / title
      Removed value: -"Force"
    • addedInput schema / properties / no_res / description
      Added value: +"Do not decode resources"
    • removedInput schema / properties / no_res / title
      Removed value: -"No Res"
    • addedInput schema / properties / no_src / description
      Added value: +"Do not decode sources"
    • removedInput schema / properties / no_src / title
      Removed value: -"No Src"
    • addedInput schema / properties / output_dir
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Custom output directory (optional)"
+}
    • addedInput schema / properties / timeout
      Added value: +{
+  "default": 300,
+  "description": "Command timeout in seconds",
+  "type": "integer"
+}
    • removedInput schema / title
      Removed value: -"decode_apkArguments"
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / properties
      Removed value: -{
-  "result": {
-    "additionalProperties": true,
-    "title": "Result",
-    "type": "object"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • removedOutput schema / title
      Removed value: -"decode_apkOutput"
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Description claims 'comprehensive validation and error handling' but is vague. With no annotations, the description carries full burden but fails to disclose side effects (e.g., file overwrites), required permissions, or execution characteristics beyond what's in the schema.

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?

Single sentence, front-loaded with the primary action. Efficient but could be more informative without becoming verbose.

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?

Given 6 parameters and a complex operation (APK decoding), the description lacks details about output location, file creation, or prerequisites. Output schema exists but description should contextualize the tool's effect.

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

Parameters3/5

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

Schema coverage is 100% with descriptions for all 6 parameters. Description adds no additional meaning, so baseline 3 is appropriate.

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?

Description uses a specific verb ('decode') and resource ('APK file'), clearly stating the tool's primary function. It lacks mention of output or distinguishing features but is unambiguous.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus siblings. Agent must infer from the name and schema. No alternatives or exclusions mentioned.

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/zinja-coder/apktool-mcp-server'

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