Skip to main content
Glama

adb_wait_stable

Waits for the Android UI to stabilize by polling the hierarchy until consecutive dumps match, helping you avoid interacting with elements during transitions or loading.

Instructions

Wait for the UI to stabilize. Polls the UI hierarchy and waits until consecutive dumps produce the same element count and structure. Useful after screen transitions, animations, or content loading before interacting with elements.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
pollMsNoPolling interval in ms (200-5000, default 500)
timeoutMsNoMaximum wait time in ms (1s-60s, default 10s)
stableCountNoNumber of consecutive identical dumps required (2-10, default 2)

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

A4/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 does explain the polling/stability criterion, which is genuinely useful behavior beyond the schema, but it omits what happens on timeout (error? success flag?), what the call returns, and whether it blocks the device or is cheap. Those are the traits an agent most needs for a waiting primitive.

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, zero waste, and the core semantic (what stability means) is front-loaded ahead of the use-case sentence. Every clause earns its place.

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 4-optional-param, annotation-free, no-output-schema tool, the description gives enough to call it correctly: purpose, mechanism, and timing context. The main omission is timeout/failure semantics, which matters for a blocking wait but is partially inferable from the timeoutMs parameter.

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%: device, pollMs, timeoutMs, and stableCount all have ranges and defaults documented in the schema. The description's mention of 'consecutive dumps' implicitly explains what stableCount counts, but adds no format or interaction detail (e.g., how timeout interacts with pollMs) beyond the schema baseline.

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 ('wait for the UI to stabilize') and immediately defines the mechanism: polling the UI hierarchy until consecutive dumps match on element count and structure. An agent can distinguish this from adb_ui_dump (one-shot dump) or adb_wait_element (waits for a specific element) without opening a schema.

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?

Gives concrete usage context: after screen transitions, animations, or content loading, and before interacting with elements. It does not name alternatives such as adb_wait_element or adb_scroll_until, which are the close siblings an agent might confuse it with, so it stops short of explicit routing.

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