Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

android_list_apps

Read-onlyIdempotent

List installed apps on the Android device. By default returns third-party apps; use all=true for all apps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNoInclude system apps. OMIT for third-party only (default false).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
channel_account_idNoAndroid device channel_account ID. Omit when the workspace has a single Android device; REQUIRED when it has more than one (e.g. WhatsApp + LINE), else the call is rejected as ambiguous.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. Changed1 schema field changed
    • changedInput schema / properties / all / description
      Previous value: -"Include system apps (default: false, third-party only)"New value: +"Include system apps. OMIT for third-party only (default false)."
  5. Changed1 schema field changed
    • addedInput schema / properties / channel_account_id
      Added value: +{
+  "description": "Android device channel_account ID. Omit when the workspace has a single Android device; REQUIRED when it has more than one (e.g. WhatsApp + LINE), else the call is rejected as ambiguous.",
+  "type": "integer"
+}
  6. Added

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 and closed-world, so safety is covered. The description adds one genuine behavioral fact beyond the annotations: the default result set is third-party apps only. It says nothing about ordering, volume, or response shape.

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?

Two tight sentences, front-loaded with what the tool does and then the default-vs-override behavior. No filler and nothing to trim.

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

Completeness4/5

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

For a no-required-parameter read tool with 100% schema coverage and annotations covering safety, the description is nearly complete. Return fields are undocumented, though there is no output schema and a list of apps is largely self-explanatory.

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%, so all three parameters (all, in_workspace, channel_account_id) are already documented in the schema. The description only restates the `all` semantics, adding no meaning beyond what structured data provides. 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?

States a specific verb+resource ('List installed apps') scoped to 'the Android device', which naturally separates it from android_launch_app, android_close_app and android_ui_dump. It is clear on its own, but never explicitly differentiates itself from any sibling tool.

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?

The description gives one useful routing rule ('use all=true for all apps') and states the default scope, but offers no guidance on when to reach for this tool versus alternatives such as android_ui_dump. Usage is implied rather than explained.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources