Skip to main content
Glama
Sign In
adb-mcp

adb-mcp

by FlashZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_package_enabled

Enable or disable an Android package via ADB's pm enable or pm disable-user commands to control app state for testing or device management.

Instructions

Enable or disable a package (pm enable / pm disable-user).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "package": "<package>",
      "enabled": "<enabled>"
    },
    "name": "set_package_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialNo
enabledYes
packageYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral burden. It discloses the underlying `pm enable` / `pm disable-user` commands, which is useful, but omits permissions needed, side effects on running apps, reversibility, and whether the change persists.

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?

A single, front-loaded sentence with zero waste. The core operation and the underlying commands are delivered immediately.

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?

Although an output schema exists and covers return values, the tool is a mutation with no annotations and 0% schema description coverage. The description is too thin to fully prepare an agent for correct invocation, especially regarding parameter semantics and side effects.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It implies the `package` and `enabled` parameters through the operation name, but says nothing about the `serial` parameter or the exact mapping of `enabled` to `pm enable` versus `pm disable-user`.

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?

States a specific operation (enable or disable a package) and maps it to the underlying `pm enable` / `pm disable-user` commands. This is clearly distinct from sibling package tools like install, uninstall, clear_app_data, and list_packages.

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 such as `uninstall` or `clear_app_data`, nor any prerequisites or exclusions. Usage is only implied by the operation name.

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