Skip to main content
Glama

adb_ci_wait_boot

Waits for an Android device or emulator to finish booting and ensures the launcher is ready, helping CI pipelines start tests only after boot completes.

Instructions

Wait for a device or emulator to fully boot. Polls sys.boot_completed and waits for the launcher to be ready. Essential for CI pipelines.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adb_ci_wait_boot"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
timeoutSecondsNoMaximum time to wait for boot in seconds (default 120)

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 are supplied, so the description carries the full behavioral burden. It usefully discloses the polling mechanism and the two conditions being awaited (boot_completed and launcher ready), but says nothing about what happens on timeout, whether the call blocks until failure, or what is returned on success versus timeout — a meaningful gap for a wait tool.

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?

Three short sentences, front-loaded with the primary action and followed by the mechanism and the target scenario; nothing is redundant. It stops short of the top mark only because a sentence on timeout/return behavior would have been a better use of the space than the somewhat promotional 'Essential for CI pipelines.'

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 two-optional-parameter, no-annotation, no-output-schema tool, the description covers purpose and mechanism adequately. What is missing is failure semantics on timeout and the expected result shape, both of which the agent needs because no structured field supplies them.

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%, with 'device' and 'timeoutSeconds' (including default 120 and 10–300 bounds) already documented in the schema, so the baseline of 3 applies. The description adds no extra meaning about device selection (e.g., behavior when omitted) or how the timeout interacts with the two polling conditions.

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 ('Wait for a device or emulator to fully boot') and adds the mechanism (polls sys.boot_completed, waits for launcher readiness), which lets an agent understand exactly what state change is being observed. It does not, however, distinguish itself from nearby siblings such as adb_ci_device_ready, adb_device_state, or adb_wait_stable, so an agent still has to infer which readiness check applies.

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?

'Essential for CI pipelines' gives a clear usage context but no explicit when-to-use/when-not or named alternative among the several readiness siblings. The agent gets a hint about the scenario, not a decision rule.

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