Skip to main content
Glama

adb_apex_list

Lists installed APEX modules on an Android device, showing each module's name, version, and active or staged status to help you audit updatable system components.

Instructions

List installed APEX modules on the device. APEX (Android Pony EXpress) modules deliver updatable system components. Shows module name, version, and active/staged status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adb_apex_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial

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.5/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; it does say the operation is a listing and specifies the returned fields (name, version, active/staged status), which is useful behavioral context. It does not state whether this is strictly read-only, whether any privilege/root level is required, or how staged-but-inactive modules are represented.

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?

Three short sentences, front-loaded with the action and resource, followed by just enough disambiguation and return-value detail. No sentence is redundant or padded.

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

Completeness3/5

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

For a small inspection tool the definition is nearly complete, and listing the return fields compensates for the missing output schema. The notable gap is the optional device parameter: with zero required parameters, the description never explains default-device selection or behavior when multiple devices are attached.

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% for the single 'device' parameter, so the schema already documents it. The description adds nothing about what happens when device is omitted (it is not required) or how a device serial is resolved, so the 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 APEX modules on the device') and the parenthetical expansion of APEX makes the subject unambiguous. It does not explicitly contrast itself with nearby siblings such as adb_list_packages or adb_package_info, so an agent must infer that this covers system-level APEX containers rather than regular apps.

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: explaining that APEX modules 'deliver updatable system components' helps an agent decide relevance, but there is no explicit when-to-use or when-not-to-use statement and no pointer to adb_list_packages / adb_package_info as the alternative for normal app inventory.

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