Skip to main content
Glama

Inspect Adb Package

inspect_adb_package
Idempotent

Retrieves version, install/update times, installer, user ID, flags, and permission count for one installed Android package via dumpsys, ignoring unknown sections. Read-only inspection.

Instructions

Inspect one installed package through dumpsys package: version name/code, install and update times, installer, user id, flags, and the requested-permission count. A fixed projection of version-dependent output; unknown sections are ignored rather than guessed. Read-only.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serial": "emulator-5554",
      "package": "com.example.app"
    },
    "name": "inspect_adb_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesDevice serial exactly as `adb devices` reports it
packageYesInstalled package to inspect

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior1/5

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

The description ends with 'Read-only', but the annotations declare readOnlyHint=false, which directly contradicts that claim and could mislead an agent about side effects. The otherwise valuable disclosure that this is 'a fixed projection of version-dependent output; unknown sections are ignored rather than guessed' cannot offset a flat contradiction with the structured safety metadata.

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 compact sentences: the first front-loads the operation and its output projection, the second covers parsing behavior and access mode. No filler, no repetition of the title.

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?

With no output schema, the description usefully enumerates the returned fields and explains how version-dependent sections are handled, which is exactly the context needed. The missing piece is the accurate side-effect/safety profile, which it gets wrong rather than omits.

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% and both parameters carry precise descriptions plus a pattern constraint and example, so the schema does the heavy lifting. The description adds no additional meaning about the serial or package format, leaving this at the baseline for fully covered schemas.

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 and resource ('Inspect one installed package through `dumpsys package`') and enumerates exactly what is returned (version name/code, install/update times, installer, user id, flags, permission count). It implicitly separates itself from list-style siblings by emphasizing 'one installed package', but never names or contrasts with `inspect_android_package` or `list_adb_packages`, so an agent must infer the boundary.

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: the phrase 'one installed package' signals the single-package case, and the closing 'Read-only' hints at a safe lookup. There is no explicit when-to-use, when-not-to-use, or named alternative for broader package enumeration or package metadata beyond dumpsys output.

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