Skip to main content
Glama
Sign In
Android Debug Bridge MCP

Android Debug Bridge MCP

by TiagoDanin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_apps

Find installed Android applications by searching for specific name patterns in app packages to identify and manage apps on connected devices.

Instructions

List installed apps matching a name pattern

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": {
      "app_name": "<app_name>"
    },
    "name": "list_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_nameYesName pattern to search for in app packages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'List' implies a read-only operation, it doesn't specify what 'matching' entails (exact match, substring, regex), whether results are filtered/limited, what format the output takes, or any performance/rate considerations. The description provides minimal behavioral context beyond the basic operation.

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 a single, efficient sentence that communicates the core functionality without any wasted words. It's appropriately sized for a simple tool with one parameter and gets straight to the point with clear front-loaded information.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't describe what the output looks like (list format, fields included), any limitations on results, error conditions, or how the pattern matching works. The agent would need to guess about important behavioral aspects of this tool.

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% with the parameter 'app_name' fully documented in the schema. The description adds the context that this is a 'name pattern to search for in app packages,' which slightly elaborates on the schema's description. However, it doesn't provide additional syntax examples, format details, or constraints beyond what the schema already states.

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 verb ('List') and resource ('installed apps') with the specific action of matching a name pattern. It distinguishes from obvious siblings like 'open_app' by focusing on listing/searching rather than launching apps. However, it doesn't explicitly differentiate from other potential list/search tools that might exist.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, limitations, or compare with other search/list tools. The agent must infer usage from the name and description alone without explicit context.

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