Skip to main content
Glama
zinja-coder

Apktool MCP Server

by zinja-coder
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

modify_resource_file

Modify the content of a specific resource file in an APKTool project, with backup and validation options for safe updates.

Instructions

Modify the content of a specific resource file with validation and backup support.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
new_contentYesNew content for the resource file
project_dirYesPath to the APKTool project directory
create_backupNoWhether to create a backup of the original file
resource_nameYesName of the resource file
resource_typeYesResource type (e.g., "layout", "values")

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 / create_backup / description
      Added value: +"Whether to create a backup of the original file"
    • removedInput schema / properties / create_backup / title
      Removed value: -"Create Backup"
    • addedInput schema / properties / new_content / description
      Added value: +"New content for the resource file"
    • removedInput schema / properties / new_content / title
      Removed value: -"New Content"
    • 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 / resource_name / description
      Added value: +"Name of the resource file"
    • removedInput schema / properties / resource_name / title
      Removed value: -"Resource Name"
    • addedInput schema / properties / resource_type / description
      Added value: +"Resource type (e.g., \"layout\", \"values\")"
    • removedInput schema / properties / resource_type / title
      Removed value: -"Resource Type"
    • removedInput schema / title
      Removed value: -"modify_resource_fileArguments"
    • 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: -"modify_resource_fileOutput"
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Mentions validation and backup support, adding context beyond the basic 'modify'. But 'validation' is vague, and backup behavior (e.g., automatic, restore) is not explained. With no annotations, the description partially carries the transparency burden.

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

Conciseness3/5

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

Single sentence, concise, but lacks additional useful structure. Could include more details without being verbose.

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

Completeness3/5

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

Adequate for a modification tool with output schema (assumed). Describes action and key features, but could explain validation and backup more thoroughly given the tool's complexity.

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 parameters are described in schema. Description adds no extra meaning beyond schema, such as format or constraints, meeting baseline.

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 clearly states it modifies a specific resource file with validation and backup, distinguishing it from read tool get_resource_file and similar modify_smali_file. However, it does not explicitly differentiate from siblings.

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 guidance on when to use this tool versus alternatives like modify_smali_file or get_resource_file. No when-not or prerequisites 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