Skip to main content
Glama

adb_a11y_touch_targets

Lists interactive Android UI elements with touch target sizes in dp and flags any below the 48dp minimum, helping identify cramped layouts that may cause tap errors.

Instructions

List all interactive elements with their touch target dimensions in dp. Highlights elements below the 48dp minimum. Useful for quickly identifying cramped UI layouts.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
belowMinOnlyNoOnly show elements below the 48dp minimum

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?

With no annotations, the description carries the full behavioral burden: it discloses that elements below 48dp are highlighted and that values are in dp, which implies a read-only listing. It omits prerequisites (screen state, foreground app), whether it triggers a UI dump, and what the response looks like, so the disclosure is partial.

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 with the core capability front-loaded and the filtering/interpretation context following. No redundant or filler wording; the only minor inefficiency is that the last sentence restates the purpose already implied by the second.

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 simple two-parameter read tool with no output schema, the description covers what the tool does and the 48dp rule, but leaves out return structure and device-state prerequisites. Adequate but not complete for an agent calling it blind.

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 both `device` and `belowMinOnly` are already documented and the baseline is 3. The description does reinforce the 48dp threshold that gives `belowMinOnly` meaning, but adds no format or default detail beyond the schema.

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 states a specific verb and resource: list interactive elements with touch target dimensions in dp, plus the 48dp threshold that defines a violation. This is enough to distinguish it from adb_a11y_tree (raw hierarchy) and adb_a11y_audit (broader audit), though it never names those siblings 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?

"Useful for quickly identifying cramped UI layouts" implies the usage context, but there is no explicit when-to-use versus adb_a11y_audit or adb_ui_find, and no statement of preconditions such as the target app needing to be in the foreground. Usage is inferred rather than directed.

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