list_appsDiscover which apps are installed on an Android device. Returns user apps by default; set system=true to include system apps.
List installed apps (user apps only unless system=true).
| Name | Required | Description | Default |
|---|---|---|---|
| device | No | ||
| system | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It does disclose the main behavioral trait, user-only filtering by default, but it says nothing about permissions, output content, or whether system=true includes both user and system apps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with no filler. It front-loads the operation and immediately qualifies the key optional behavior with a conditional.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple, has only optional parameters, and an output schema exists, so the core call is close to self-evident. However, the missing explanation of the device parameter and the lack of any sibling differentiation leave meaningful gaps for an agent choosing and invoking this tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description must compensate. It explains the system parameter's default and effect, but the device parameter is left entirely to inference from its name and null default.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: "List installed apps". The clause "user apps only unless system=true" immediately adds a scoping distinction that separates it from lookup or launch tools among the siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to choose this tool over alternatives such as lookup_app or launch_app. The "unless system=true" condition is parameter behavior, not a usage guideline, and the device parameter is not addressed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.