Skip to main content
Glama

adb_list_splits

Lists all installed APK split paths for a package, including the base APK and language, screen-density, and ABI configuration splits, so you can inspect app bundle components on a device.

Instructions

List all APK split paths installed for a package. Shows the base APK and any configuration splits (language, screen density, ABI).

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": {
      "packageName": "<packageName>"
    },
    "name": "adb_list_splits"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
packageNameYesPackage name (e.g., 'com.example.app')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'List' strongly implies a read-only, non-destructive operation and the second sentence discloses what the result contains, but nothing is said about behavior when the package is not installed, whether the device parameter defaults to the single connected device, or any permission requirements.

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?

Two short sentences, zero filler, with the core purpose front-loaded and the elaboration of return contents following immediately. Nothing here is redundant or padded.

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 simple two-parameter read-only listing tool with full schema coverage and no output schema, the description covers what it does and roughly what it returns. The only meaningful gap is device-selection behavior when the serial is omitted.

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 both parameters (device serial, packageName) are documented with an example, so the description does not need to compensate. The description adds nothing beyond the schema about parameter behavior — notably it does not say what happens if device is omitted with multiple devices attached.

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?

States a specific verb and resource ('List all APK split paths installed for a package') and clarifies the returned contents: base APK plus configuration splits by language, density, and ABI. That distinguishes it well from adb_list_packages and adb_package_info, though it never names those siblings explicitly.

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 is only implied: an agent can infer it is for inspecting split APK structure of an installed package, but there is no explicit when-to-use or when-not-to-use guidance, and no pointer to alternatives such as adb_package_info or adb_extract_apks.

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