Skip to main content
Glama

classify_apk_protection

Scans APK and DEX files for obfuscation, packers, and SSL pinning patterns using a signature catalog, returning categorized matches with evidence offsets.

Instructions

Walk the APK + every classes*.dex for known protection patterns.

Uses the vendored data/apkid-signatures.json catalog. Returns a list of {category, evidence, evidence_offset, evidence_file} records with category-only labels ("apk_packager", "dex_obfuscator", "ssl_pinning", etc.). The category names describe observable patterns; no specific commercial product is named.

Args: path: path to the APK max_per_category: per-category match cap (default 50)

Returns::

{
  "path": "...",
  "matches": [{"category": "...", "evidence": "...",
               "evidence_offset": N, "evidence_file": "...",
               "match_pattern": "...", "id": "..."}, ...],
  "by_category": {"dex-obfuscator": 12, "ssl_pinning": 2, ...},
  "truncated": {"per_category": bool}
}

The signature table is matched against:

  • classes.dex string table (DEX class names + method signatures + string literals);

  • every lib/*.so for the native-section + string-literal categories;

  • the manifest's application / meta-data elements.

The implementation lives in servers/re-apktool/src/re_apktool/classify.py.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
max_per_categoryNo
Behavior4/5

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

With no annotations, the description carries full burden. It details the matching process against classes.dex, lib/*.so, and manifest, and describes return format. It is transparent about the tool's behavior, though it could explicitly state it is read-only.

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?

The description is well-structured with a summary, parameter details, return format, and matching targets. It is front-loaded with the purpose. Slightly verbose but every sentence adds value.

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

Completeness4/5

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

Given no output schema, the description provides a detailed return structure including fields like category, evidence, and truncation info. It covers the tool's complexity adequately, though missing edge case handling notes.

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 description coverage is 0%, but the description provides clear explanations for both parameters: 'path: path to the APK' and 'max_per_category: per-category match cap (default 50)'. This compensates well for the lack of schema descriptions.

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 walks APK and classes.dex for known protection patterns. It distinguishes from sibling tools like decode_manifest or list_dex_classes by specifying its unique function of classifying protection patterns.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. Although sibling tool names are given, the description itself lacks context for selection, which is necessary for an AI agent to choose correctly.

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/Heretek-RE/re-apktool'

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