Skip to main content
Glama

adb_a11y_tree

Dumps an accessibility-focused UI hierarchy for screen readers, listing relevant roles, labels, states, and navigation order while filtering decorative layout containers.

Instructions

Dump the accessibility-focused view of the UI hierarchy. Shows only elements relevant to screen readers: their roles, labels, states, and navigation order. Filters out decorative/layout containers.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial

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 behavioral burden. It does disclose meaningful traits — the filtering of decorative containers and the returned fields (roles, labels, states, navigation order) — but says nothing about prerequisites (foreground app, unlocked screen, accessibility service enabled), output format, or the underlying uiautomator cost.

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 core action and immediately followed by scope and filtering behavior. No filler, though the third sentence could have been merged into the second without loss.

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 one-parameter read tool with no output schema, the description covers what is returned and what is excluded, which is most of what an agent needs. The remaining gap is prerequisite/environment context rather than anything structural.

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?

The single optional parameter 'device' is fully documented in the schema ('Device serial') at 100% coverage, so the schema already does the work. The description adds no semantics about device selection, defaulting, or behavior when omitted.

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 ('Dump') and resource ('accessibility-focused view of the UI hierarchy'), and the second sentence clarifies exactly what subset is returned. It implicitly separates itself from the full-hierarchy sibling adb_ui_dump by saying it filters out decorative/layout containers, but it never names that sibling 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?

Usage is only implied: 'elements relevant to screen readers' suggests accessibility testing, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives like adb_ui_dump, adb_a11y_audit, or adb_a11y_touch_targets, all of which sit close to this tool in the sibling list.

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