Skip to main content
Glama

adb_list_permissions

Inspect declared and granted permissions for an Android package and filter by granted/denied status to audit permission state before or after grant or revoke operations.

Instructions

List permissions declared and granted for a package. Parses the package dump to show install-time and runtime permissions with their current grant state. Useful for auditing permission state before and after grant/revoke operations.

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": {
      "packageName": "<packageName>"
    },
    "name": "adb_list_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
filterNoShow all permissions, only granted, or only denied (default: all)all
packageNameYesPackage name (e.g., 'com.example.app')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the data source (package dump parsing) and the shape of what is reported (install-time vs runtime permissions, grant state), which implies a safe read. It says nothing about failure modes (unknown/uninstalled package), required device state, or output formatting, leaving meaningful gaps for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and ending with the use case. Every sentence carries information; there is no filler, though the second sentence mildly restates the first's 'declared and granted' framing.

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 3-parameter read tool with no annotations and no output schema, the description usefully compensates by naming the returned permission categories and grant state. Edge-case behavior (nonexistent package, behavior when the filter matches nothing) remains undocumented but is a minor gap at this complexity.

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 (device, filter, packageName) are already documented, including the enum values and default for filter. The description adds no parameter-level semantics such as how device defaults are resolved or how filter interacts with the reported classification, so 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?

The description states a specific verb and resource ('List permissions declared and granted for a package') and adds the mechanism ('parses the package dump') plus the data shown ('install-time and runtime permissions with their current grant state'). It does not explicitly distinguish itself from near-neighbors such as adb_permission_audit or adb_grant_permission, so it falls short of 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 Guidelines3/5

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

'Useful for auditing permission state before and after grant/revoke operations' implies the workflow context, which is better than nothing. However, it never names an alternative tool (e.g., adb_permission_audit, adb_grant_permission) or states when not to use this one, so selection among siblings is left to inference.

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