Skip to main content
Glama
Sign In
@wilsonbeam/openclaw-adb-mcp

@wilsonbeam/openclaw-adb-mcp

by wilsonbeam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

adb_list_packages

List installed Android packages, filtering by system, third-party, or all, to identify apps on a connected device.

Instructions

List installed packages on the device

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_list_packages"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoFilter packages by type
deviceIdNoTarget device ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It only states the action without disclosing return format, default filter behavior, or device selection rules. This leaves significant ambiguity for the agent.

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 one concise sentence, front-loaded with the main verb and object, and contains no redundant words.

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

Completeness2/5

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

Given the tool has two parameters and no output schema, the description is incomplete. It doesn't explain what 'packages' means (names vs. details), the default filter, or how deviceId resolves with multiple devices.

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?

The schema covers 100% of parameters with descriptions (filter enum, deviceId optional), so the baseline is 3. The description adds no extra meaning beyond the schema.

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 clearly states the tool lists installed packages, with a specific verb and resource. It distinguishes from siblings like adb_list_devices, but doesn't mention the filter option, so it's slightly less complete than a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives like adb_shell, which could also list packages via pm list. No prerequisites, examples, or exclusions are given.

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