Skip to main content
Glama

adb_resolve_intents

Inspect an Android package to list registered activities, services, and receivers with their intent filters, helping identify how it handles intents.

Instructions

Discover all activities, services, and receivers registered by a package with their intent filters

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
packageNameYesPackage name to query

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

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load. 'Discover' signals a non-mutating query and the description states what is enumerated, which is useful behavioral context, but it says nothing about whether the package must be installed, whether root or debuggable builds are required, or what happens on an unknown package.

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?

One tight sentence with the resource front-loaded and no filler. The trailing 'with their intent filters' is slightly ambiguous in attachment but does not cost the reader anything material.

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 low-risk, two-parameter read-only query the description is serviceable: it names the returned component types. However, with no output schema, it does not indicate the shape of the results (component names, filter actions/categories) or whether results are grouped, leaving some uncertainty about what comes back.

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 are already documented in the schema. The description's phrase 'by a package' reinforces packageName but adds no format or semantics beyond the schema, and the 'device' parameter is not referenced at all. 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 gives a specific verb ('Discover') and a concrete resource ('activities, services, and receivers registered by a package with their intent filters'). That is precise enough for an agent to distinguish it from adb_package_info or adb_list_packages, though it never names those siblings explicitly.

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?

Use is only implied: an agent can infer this is the tool for enumerating a package's manifest components. There is no statement of when to prefer it over adb_package_info, adb_list_packages, or adb_test_gen_from_intents, and no exclusions or prerequisites are given.

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