Apktool MCP Server

by zinja-coder

Overview Schema Source Related Servers Discussions Admin

Python

Local

list_smali_files

List smali files in an Apktool project with pagination support and optional filtering by package prefix.

Instructions

List smali files with pagination support and enhanced filtering.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No	Number of items to return (0 means use default)
`offset`	No	Starting offset for pagination
`smali_dir`	No	Which smali directory to use (smali, smali_classes2, etc.)	smali
`project_dir`	Yes	Path to the APKTool project directory
`package_prefix`	No	Optional package prefix to filter by (e.g., "com.example")

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv1.0.1Jul 5, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / count

Added value: +{
+  "default": 0,
+  "description": "Number of items to return (0 means use default)",
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Starting offset for pagination",
+  "type": "integer"
+}

addedInput schema / properties / package_prefix / description

Added value: +"Optional package prefix to filter by (e.g., \"com.example\")"

removedInput schema / properties / package_prefix / title
```
Removed value: -"Package Prefix"
```
addedInput schema / properties / project_dir / description
```
Added value: +"Path to the APKTool project directory"
```
removedInput schema / properties / project_dir / title
```
Removed value: -"Project Dir"
```

addedInput schema / properties / smali_dir / description

Added value: +"Which smali directory to use (smali, smali_classes2, etc.)"

removedInput schema / properties / smali_dir / title
```
Removed value: -"Smali Dir"
```

removedInput schema / title

Removed value: -"list_smali_filesArguments"

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: -"list_smali_filesOutput"

First observedv1.0.0Aug 14, 2025

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided, so description must cover behavioral traits. It mentions pagination and filtering but omits details like read-only nature, performance implications, or error conditions.

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?

The description is succinct with no redundant words. It conveys the core purpose in a single sentence.

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 the presence of an output schema and full parameter descriptions, the description is largely complete. However, it lacks an explanation of what 'enhanced filtering' entails, which could affect usage.

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%, so baseline is 3. Description adds no further meaning beyond the schema; 'enhanced filtering' is vague and not elaborated.

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 'List smali files' with pagination and filtering. It distinguishes from sibling 'list_smali_directories' which lists directories, not files.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives like 'get_smali_file' or 'list_smali_directories'. Usage is implied but not clarified.

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

Deploy Server