Skip to main content
Glama
Neem2004

Android ADB MCP Server

by Neem2004
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

adb_list_packages

List installed Android packages, optionally filtering by case-insensitive name substring and including system packages.

Instructions

Lists the packages installed on the Android device (third-party only by default), optionally filtered by a case-insensitive name substring and including system packages. / Lista los paquetes instalados del dispositivo Android (solo de terceros por defecto), con filtro opcional por subcadena del nombre sin distinguir mayúsculas y opción de incluir paquetes de sistema.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoOnly list packages whose name contains this text (case-insensitive). / Lista solo paquetes cuyo nombre contenga este texto (sin distinguir mayúsculas).
include_systemNoIf true, include system packages; if false or omitted, only third-party packages are listed. / Si es true, incluye paquetes de sistema; si es false u omitido, solo lista paquetes de terceros.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.1
    • changedInput schema / properties / filter / description
      Previous value: -"Filtra los paquetes por texto en el nombre."New value: +"Only list packages whose name contains this text (case-insensitive). / Lista solo paquetes cuyo nombre contenga este texto (sin distinguir mayúsculas)."
    • addedInput schema / properties / filter / examples
      Added value: +[
+  "com.example",
+  "google"
+]
    • addedInput schema / properties / include_system / default
      Added value: +false
    • changedInput schema / properties / include_system / description
      Previous value: -"Si es true, incluye paquetes de sistema (sin -3)."New value: +"If true, include system packages; if false or omitted, only third-party packages are listed. / Si es true, incluye paquetes de sistema; si es false u omitido, solo lista paquetes de terceros."
    • addedInput schema / properties / include_system / examples
      Added value: +[
+  true,
+  false
+]
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It clearly discloses the default third-party-only behavior, the case-insensitive filter, and the include_system option. It does not explicitly state side-effect-freedom or output format, but 'Lists' strongly implies a read-only operation.

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 compact, front-loaded with the core action, and contains no filler. The bilingual repetition is reasonable and does not bloat the message.

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

Completeness5/5

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

For a simple two-parameter, no-output-schema tool, the description covers the behavior, defaults, and optional parameters. Nothing an agent needs to call it correctly is missing.

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%, so the schema already fully documents both parameters. The description adds little beyond the schema, mostly restating filter behavior and the default for include_system. This matches the baseline for full schema coverage.

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 uses a specific verb ('Lists') and resource ('packages installed on the Android device'), then clearly states default scope and optional behaviors. It is immediately distinguishable from the sibling tools, which target logcat, hierarchy, and shell execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the intended use clear: list installed packages, optionally filtered, optionally including system packages. It does not explicitly name alternatives or say when not to use it, but the sibling tools are distinct enough that little confusion remains.

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