Skip to main content
Glama

List Adb Packages

list_adb_packages
Idempotent

Lists installed Android packages on a specified device, including each base APK's device filesystem path, and can filter to third-party or system packages.

Instructions

List installed packages on one device with each base APK's device path, optionally scoped to third-party or system packages. Paths are device filesystem paths, not host-local. Read-only.

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": {
      "scope": "third_party",
      "serial": "emulator-5554"
    },
    "name": "list_adb_packages"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoPackage scope: all packages, third-party only (-3), or system only (-s)
serialYesDevice serial exactly as `adb devices` reports it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

The note that "paths are device filesystem paths, not host-local" is genuinely useful disambiguation not present in the schema. However, the closing claim "Read-only" conflicts with the supplied readOnlyHint=false annotation; the description asserts a read-only operation the metadata does not endorse. The damage is limited because destructiveHint=false and idempotentHint=true are consistent with the described behavior, but the agent receives mixed safety signals.

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?

Three short sentences, front-loaded with the core action and the most error-prone detail (device vs host paths). The trailing two-word "Read-only." fragment is both the least substantive sentence and the source of the annotation conflict, which a tighter definition would not have added.

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?

With only two parameters, full schema coverage, and no output schema, the description carries the main burden of describing return content, and it does so by noting each base APK's device path and the scope filter. It does not describe output ordering, truncation, or behavior on a disconnected device, which is a modest gap for a shell-backed adb tool flagged as open-world.

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 serial format ("exactly as adb devices reports it") and the scope enum are already fully documented in the schema. The description echoes the scope concept but adds no syntax, default, or format detail beyond what the schema supplies; baseline 3 applies.

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?

The description gives a specific verb and resource ("List installed packages on one device") plus the payload shape ("each base APK's device path") and an optional scope. It is clear on its own, but it never names or distinguishes itself from close siblings such as resolve_adb_packages or inspect_adb_package, so an agent must infer the boundary.

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?

"Optionally scoped to third-party or system packages" implies when the scope argument is useful, and "on one device" implies single-device targeting. There is no explicit when-to-use guidance, no statement about when to prefer a package-inspection or package-resolution sibling, and no prerequisite discussion beyond the serial requirement.

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