Skip to main content
Glama

adb_package_info

Retrieve installed Android package details—version, permissions, and file paths—to inspect app configuration or troubleshoot issues.

Instructions

Get detailed info about an installed package (version, permissions, paths)

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_package_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
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. Changed2 schema fields changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / packageName / description
      Previous value: -"Package name"New value: +"Package name (e.g., 'com.example.app')"
  3. First observedv1.1.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations present, the description carries the full disclosure burden. 'Get' and 'installed' imply a read-only lookup scoped to already-installed packages, and the parenthetical previews the returned fields, but it says nothing about failure behavior for missing packages, root/permission requirements, 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?

A single front-loaded sentence with the resource named before the returned fields. No filler, no redundancy.

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 two-parameter, no-output-schema tool the description does a fair job by listing the returned data. However, with no annotations and no output schema, it should also cover the device default and what happens when the package is not installed.

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 coverage is 100%, so both parameters (device serial and packageName with an example) are already documented in the schema, and the baseline of 3 applies. The description adds only the constraint that the package must be installed, not additional format or defaulting semantics.

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 pairs a specific verb ('Get detailed info') with a precise resource ('an installed package') and enumerates the content returned (version, permissions, paths). It is clearly distinct from the many other adb_* siblings, though it never explicitly contrasts itself with adb_list_packages or adb_dumpsys.

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?

Usage is only implied by the phrase 'installed package' – the agent must infer that this is the per-package detail lookup rather than the bulk listing. No when-to-use, when-not-to-use, or prerequisite guidance is provided despite ~130 sibling tools including adb_list_packages, adb_list_permissions and adb_dumpsys.

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