Skip to main content
Glama

Resolve Adb Packages

resolve_adb_packages
Idempotent

Resolve installed Android packages by case-insensitive name substring and return each match's base APK path, so you can pull the exact package next.

Instructions

Find installed packages by case-insensitive substring of the package name (e.g. whatsapp → com.whatsapp), returning each match's base APK device path. The first step of an easy get: resolve, then pull_adb_package the exact name. 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": {
      "query": "whatsapp",
      "serial": "emulator-5554"
    },
    "name": "resolve_adb_packages"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCase-insensitive substring matched against installed package names (e.g. whatsapp)
serialYesDevice serial exactly as `adb devices` reports it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior1/5

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

The description says "Read-only," but the annotations declare readOnlyHint=false. That is a direct contradiction on a core behavioral trait, so the description cannot be trusted for safety classification. It also does not clarify why the tool is marked non-read-only despite appearing to be a lookup.

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 with the core behavior front-loaded, followed by the workflow context. No wasted wording.

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 two-parameter lookup tool with no output schema, the description covers purpose, matching behavior, return value, and workflow. The only significant gap is the unresolved contradiction with the readOnlyHint annotation.

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 both parameters are already documented in the schema. The description reinforces the query semantics with an example and mentions the return value, but adds little parameter meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: find installed packages by case-insensitive substring, returning each match's base APK device path. The example (`whatsapp` → `com.whatsapp`) makes the scope concrete and distinguishes it from a plain package listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly positions the tool as the first step of a two-step workflow: resolve, then call pull_adb_package with the exact name. It does not explicitly say when to prefer list_adb_packages instead, but the intended usage context is clear.

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