Skip to main content
Glama

android_apps

Read-onlyIdempotent

Lists installed Android app package IDs on a connected phone, with an option to return only user-installed apps and target a specific device.

Instructions

List installed application package IDs, optionally only user-installed apps.

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": "android_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoOptional connected device id, connection serial or exact model. Overrides the selected/default phone for this call.
userOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered. The description adds little beyond the name, and its phrase 'optionally only user-installed apps' obscures the actual default (userOnly defaults to true, i.e. system apps are excluded unless overridden) — a meaningful behavioral detail left unstated.

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?

A single front-loaded sentence with no filler; the output (package IDs) and the optional filter are both stated up front.

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 simple two-parameter read-only tool with no output schema, the description is close to adequate, but the return format (plain package ID strings vs objects) and the true default scope are left for the agent to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: 'device' is documented in the schema while 'userOnly' has no schema description, so the description must carry that one — and it does explain that userOnly filters to user-installed apps. It loses a point for calling it optional when the default is true, which misleads about the default result set.

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?

Specific verb plus resource: 'List installed application package IDs' tells the agent exactly what is returned, and 'user-installed apps' scopes it further. It does not name or contrast any sibling (e.g. android_open_app), but the purpose is unmistakable from the verb and resource.

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 this is the tool to call when it needs package IDs (e.g. before android_open_app), but the description states no when-to-use condition, no prerequisites for obtaining a device, and no exclusions or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.