Skip to main content
Glama

adb_a11y_audit

Audit the current Android screen for accessibility issues such as missing labels, small touch targets, unlabeled images, and focus issues; return a structured report with severity and rule violations.

Instructions

Run an automated accessibility audit on the current screen. Checks for: missing labels on interactive elements, undersized touch targets (<48dp), images without content-descriptions, clickable elements missing focusability, and duplicate descriptions. Returns a structured report with severity and rule violations.

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

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 bears the full behavioral burden, and it does disclose the five rule categories and the shape of the result (severity plus rule violations). It omits other relevant traits: that the operation is non-destructive/read-only, what happens if the screen is mid-transition, and how large the report can get on a dense screen with many violations.

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?

Two sentences, front-loaded with the action, and the rule list is compact and scannable rather than prose. There is no filler, though the closing sentence about the return value is slightly generic ("structured report") where a concrete field hint would have earned the space.

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 single-optional-parameter, non-destructive audit with no output schema, the description covers what is checked and roughly what comes back, which is enough to invoke it confidently. The residual gap is that without an output schema, the report's actual structure and severity levels remain underspecified.

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% and there is only one optional parameter (device serial), so the schema already carries the semantics and the baseline of 3 applies. The description adds no meaning beyond it, not even clarifying which device is audited when the serial is 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?

The description uses a specific verb and resource ("Run an automated accessibility audit on the current screen") and itemizes the exact rule categories checked, so the agent knows precisely which capability this is. It falls short of a 5 because two sibling tools in the same family (adb_a11y_touch_targets, adb_a11y_tree) overlap in scope and are never named or differentiated.

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?

Scope is implied ("on the current screen"), which tells the agent the audit applies to the foreground UI rather than the whole app. However, there is no explicit guidance on when to choose this composite audit over adb_a11y_touch_targets or adb_a11y_tree, nor any stated prerequisites such as a connected device or a screen that has finished rendering.

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