Skip to main content
Glama

adb_ci_run_tests

Run Android instrumented tests (androidTest) via am instrument and capture results. Returns structured pass/fail output.

Instructions

Run Android instrumented tests (androidTest) via am instrument and capture results. Returns structured pass/fail output.

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": {
      "testPackage": "<testPackage>"
    },
    "name": "adb_ci_run_tests"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
runnerNoTest runner class (default: AndroidX JUnit runner)androidx.test.runner.AndroidJUnitRunner
timeoutNoTimeout in ms (10s-10min, default 5 min)
testClassNoSpecific test class to run (optional)
testMethodNoSpecific test method (requires testClass)
testPackageYesTest package (e.g., 'com.example.app.test')

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

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

With no annotations, the description carries the full burden. It usefully discloses that results are captured and returned as 'structured pass/fail output', but omits key behavior for a test runner: whether it blocks until completion (only implied by the timeout param), what happens on device disconnect or runner crash, and whether the test package must already be installed.

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 short sentences, front-loaded with the action and mechanism, followed by the return-value note. Nothing is repeated or wasted.

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 six-parameter execution tool with no annotations and no output schema, the description covers what it does and roughly what it returns but leaves operational gaps: prerequisites, blocking semantics, and failure reporting. Adequate minimum viable, not complete.

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 every parameter (device, runner, timeout, testClass, testMethod, testPackage) is already documented with defaults and ranges. The description adds no parameter-level meaning 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?

States a specific verb ('Run') plus resource ('Android instrumented tests (androidTest)') and even names the underlying mechanism ('am instrument'), which separates it from Gradle-driven siblings like adb_gradle or adb_build_and_install. It does not explicitly name a competing sibling (adb_farm_run, adb_multi_test, adb_test_session_start), so it stops short of a 5.

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?

The mechanism mention implies context: use this to execute already-built instrumented tests on a connected device rather than rebuilding. But there is no explicit when-to-use/when-not-to-use statement and no mention of prerequisites (test APK installed, device booted) or alternatives such as adb_farm_run or adb_test_session_start for multi-device/stepwise flows.

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