Skip to main content
Glama
Neem2004

Android ADB MCP Server

by Neem2004
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

adb_list_packages

List installed Android packages, third-party only by default, with optional case-insensitive name filter and system package inclusion.

Instructions

Lists the packages installed on the Android device as one 'package:' line each (third-party only by default). Optionally filters by a case-insensitive name substring and includes system packages. / Lista los paquetes instalados del dispositivo con una línea 'package:' por cada uno (solo de terceros por defecto). Filtra opcionalmente por subcadena del nombre sin distinguir mayúsculas e incluye 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. Changed2 schema fields changedv1.0.2
    • addedInput schema / properties / filter / title
      Added value: +"filter"
    • addedInput schema / properties / include_system / title
      Added value: +"include_system"
  2. 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
+]
  3. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key behavioral facts: the default filter to third-party packages, the per-package line format, and case-insensitive matching. It stops short of stating the device-connection precondition or what happens when no device is attached, which are the main remaining unknowns for this kind of ADB tool.

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?

The content is front-loaded and each clause is useful, but the description is given twice (English and Spanish), doubling the token footprint without adding information for an agent. The bilingual duplication is defensible for localization yet pure redundancy from a selection standpoint.

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 two-optional-parameter read tool with no output schema, the description covers the operation, defaults, filtering, and exact return line shape, which is most of what an agent needs. Only the environmental precondition (a connected/unlocked device) and failure behavior are absent.

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%: both 'filter' and 'include_system' are fully documented with defaults, examples, and case-sensitivity semantics in the schema itself. The description restates that same information rather than adding syntax, edge cases, or interaction rules, so the baseline 3 applies.

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 states a specific verb and resource ('Lists the packages installed on the Android device') and even specifies the exact output line format ('package:<name>' one per line). It is the only listing/packages tool among the siblings, so an agent can place it immediately against adb_get_logcat, adb_dump_hierarchy, and adb_execute_shell.

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?

It clearly states the default scope (third-party only) and the two ways to narrow or widen results (case-insensitive substring filter, include_system). It does not, however, say when an alternative should be preferred — e.g., that adb_execute_shell is the route for other package operations — so the guidance is contextual rather than exclusive.

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