Skip to main content
Glama

adb_test_gen_from_intents

Generate an Android test workflow by analyzing a package's registered activities and intent filters; launch each exported activity, verify rendering, and output JSON compatible with adb_workflow_run.

Instructions

Analyze a package's registered activities and intent filters to generate a test workflow that launches each exported activity and verifies it renders. Produces workflow JSON compatible with adb_workflow_run.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
packageNameYesPackage name to analyze

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.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does disclose the analysis target (exported activities and intent filters), the generation behavior, and the output format. However, it does not say whether the tool only reads the device or also mutates/persists anything, whether a device must be connected, or whether it actually runs the generated workflow. These are 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.

Conciseness5/5

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

Two sentences, no filler, and the core action is front-loaded before the output-compatibility note. Every clause contributes new information.

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 simple two-parameter, non-annotated tool this is close to sufficient: it states the input concept, the transformation, and the output artifact. The remaining gap is that with no output schema, the description doesn't clarify whether the workflow JSON is returned inline or written somewhere, nor the device requirement.

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% for both parameters (device serial, package name to analyze), so the schema already does the semantic work. The description adds context about what the package is analyzed for but no format or constraint detail beyond the schema, so the 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+resource pair: analyze a package's registered activities and intent filters, then generate a test workflow. It also frames the output as workflow JSON compatible with adb_workflow_run, which differentiates it from runners. It stops short of distinguishing it from the closest sibling, adb_test_gen_from_ui.

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 mention of compatibility with adb_workflow_run suggests a generate-then-run pipeline, but there is no explicit 'use this when' statement, no comparison to adb_test_gen_from_ui or adb_test_gen_save, and no prerequisites or exclusions (e.g. what happens if no exported activities exist).

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