Skip to main content
Glama

Install Adb Package

install_adb_package
Destructive

Installs a local APK on an Android device via adb, with optional replace mode that keeps existing app data, and records the APK digest, size, and device install verdict.

Instructions

Install one local APK on the device (adb install [-r]), recording the APK's host digest and byte size. A device-mutating tool: replace re-installs over an existing package while keeping its data; the device's own Success/Failure verdict is preserved with its reason.

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": {
      "serial": "emulator-5554",
      "apk_path": "/tmp/app.apk"
    },
    "name": "install_adb_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesDevice serial exactly as `adb devices` reports it
replaceNoReplace an existing installation and keep its data (adb install -r)
apk_pathYesExisting local APK file to install

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, yet the description still adds real value: it labels the tool device-mutating, explains that `replace` preserves existing app data (what survives vs. what is destroyed), and notes that the device's Success/Failure verdict and reason are preserved as output.

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, correctly front-loaded with the action and the `[-r]` mapping before the behavioral caveat; no filler, though the parenthetical command notation and digest/size note make it slightly information-heavy for its length.

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?

For a destructive, three-parameter mutation tool with full annotation coverage and no output schema, the definition covers the mutation risk, the replace semantics, and the shape of the returned verdict; only edge cases such as a missing or invalid APK path or timeout behavior are left unaddressed.

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 description coverage is 100% and the schema already documents `serial`, `apk_path`, and the `replace` flag with its `adb install -r` mapping, so the description's explanation of `replace` largely restates structured data rather than adding new syntax or constraint detail.

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 verb and resource ('Install one local APK on the device'), names the underlying command form (`adb install [-r]`), and scopes it to a single APK, which cleanly separates it from siblings like uninstall_adb_package and inspect_adb_package.

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?

Usage context is implied by the phrase 'Install one local APK' and by the explanation of when to set `replace`, but the description never explicitly says when to choose this over siblings such as push_adb_file or when reinstalling should be preceded by uninstall_adb_package.

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