Skip to main content
Glama

Decode Android Resources

decode_android_resources
Idempotent

Decode a local APK's resources to inspect readable AndroidManifest.xml, version/SDK facts, string resources, and available locales without recovering Java source from smali.

Instructions

Decode one local APK's resources with apktool d --no-src in a provider-owned workspace that is removed after projection: the readable AndroidManifest.xml, apktool.yml version and SDK facts, the app's string resources (default or one locale, bounded to 2000 entries), available string locales, and the decoded file count. The target APK is digest with SHA-256 before decoding; smali is skipped because Java-source recovery belongs to the JADX family.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "/targets/Example.apk"
    },
    "name": "decode_android_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesLocal APK file to decode
localeNoProject strings from res/values-<locale>/strings.xml instead of the default table
include_stringsNoProject res/values/strings.xml entries (bounded to 2000 entries)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare openWorldHint/idempotentHint/destructiveHint, but the description adds non-obvious behavior the schema cannot express: a provider-owned workspace that is removed after projection, SHA-256 digesting of the target APK before decoding, and a 2000-entry bound on projected strings. This explains why readOnlyHint is false despite the tool being non-destructive. It does not cover failure modes (corrupt or non-APK input) or what happens when the locale table is absent.

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 dense sentences, front-loaded with the action and mechanism, followed by the output inventory and the sibling boundary. The output enumeration is long but each item is informational; there is minimal filler, though the value list could be tightened into a shorter clause.

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?

There is no output schema, and the description compensates by enumerating the full projection surface (manifest, apktool.yml facts, bounded strings, locale list, file count). Combined with the workspace lifecycle, digest step, and entry cap, an agent has enough to call this correctly and set expectations for the result.

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 the baseline would be 3; the description earns more by clarifying that strings come from the default table or exactly one locale table and are capped at 2000 entries, and that available string locales are reported as an output. It still doesn't explain how `include_strings` interacts with `locale` (e.g., whether locale is ignored when strings are excluded).

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?

Names a specific verb ("Decode") and a precisely bounded resource ("one local APK's resources" via `apktool d --no-src`), then enumerates exactly what is produced: AndroidManifest.xml, apktool.yml version/SDK facts, string resources, locales, and decoded file count. It also draws a hard boundary against the JADX family for smali/Java-source recovery, so an agent can distinguish it from sibling decompilation tools without opening a schema.

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?

Gives clear operating context (single local APK, `--no-src`, smali explicitly skipped because Java-source recovery belongs to the JADX family), which functions as both a when-to-use and a partial when-not-to-use signal. It stops short of naming specific sibling alternatives for manifest-only or string-only inspections, so routing beyond the JADX distinction 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