Skip to main content
Glama

Robot Actions — Remote Device Control

android_accessibility_audit

Run an accessibility audit on the CURRENT screen of an Android device. Checks match the rules Google's own Accessibility Scanner applies, so findings line up with what Android developers already act on. Audits whatever is in the foreground right now, so navigate to the screen you care about FIRST (device_tap_by_text / device_launch_app), then call this. Reports tap targets below the recommended minimum, several tappable elements stacked on identical bounds (the screen reader announces the same thing twice), controls that report a button class but expose no click action (the screen reader announces a button the user cannot activate), actionable controls the screen reader cannot name at all (no text, no description, no labelled child — the classic unlabelled icon button), descriptions that redundantly restate the element's type, state or action ("Submit button" — the screen reader says "button" already), and controls reporting a class assistive technology cannot interpret. Each finding carries the element's label, class and pixel rect — the rect centre is directly tappable with device_tap. Pass scroll:true to keep scrolling and re-auditing until nothing new comes into view, so content below the fold is covered too. IMPORTANT LIMITS, so findings are read correctly: tap-target results are a screening signal, not a verdict, because a control can legitimately extend its own tap area in a way this audit cannot observe; only elements actually drawn on screen are examined; and an element made tappable purely by an ancestor's touch dispatch is invisible here unless its own class is a control class. Contrast and text-size are NOT checked — that needs data this audit cannot read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
udidYesDevice serial number (UDID)
checksNoChecks to run; omit for all. "TouchTargetSize" = tap targets below the recommended minimum; "DuplicateClickableBounds" = several tappable elements on identical bounds; "MissingClickAction" = a button-class element exposing no click action; "SpeakableTextPresent" = an actionable control with no text, content description or labelled descendant; "RedundantDescription" = description restates type/state/action; "ClassName" = control reports an uninterpretable class.
scrollNoDefaults false. When true, audit the screen, scroll down, and audit again — repeating until a pass reveals no new elements or maxScrollSteps is reached — then report the deduplicated union. This CHANGES THE SCREEN: it scrolls the app and does not scroll back, and on a lazily-loaded list it will trigger loading. Leave it off when the app must not be disturbed.
maxScrollStepsNoOnly with scroll:true. Maximum scrolls before stopping regardless (default 6, max 20).
localeIsEnglishNoDefaults true. The redundant-description check matches English words, so set false on a non-English device to skip it rather than have it compare English words against other-language text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / scroll / description
      Previous value: -"Defaults false. When true, audit the screen, scroll down, and audit again — repeating until a pass reveals no new elements or maxScrollSteps is reached — then report the deduplicated union. This CHANGES THE SCREEN: it scrolls the app and does not scroll back, and on a lazily-loaded list it will trigger loading. Leave it off when the app must not be disturbed."New value: +"Defaults false. When true, audit the screen, scroll down, and audit again — repeating until a pass reveals no new elements or maxScrollSteps is reached — then report the deduplicated union. This CHANGES THE SCREEN: it scrolls the app and does not scroll back, and on a lazily-loaded list it will trigger loading. Leave it off when the app must not be disturbed."
  2. Changed1 schema field changed
    • changedInput schema / properties / scroll / description
      Previous value: -"Defaults false. When true, audit the screen, scroll down, and audit again — repeating until a pass reveals no new elements or maxScrollSteps is reached — then report the deduplicated union. This CHANGES THE SCREEN: it scrolls the app and does not scroll back, and on a lazily-loaded list it will trigger loading. Leave it off when the app must not be disturbed."New value: +"Defaults false. When true, audit the screen, scroll down, and audit again — repeating until a pass reveals no new elements or maxScrollSteps is reached — then report the deduplicated union. This CHANGES THE SCREEN: it scrolls the app and does not scroll back, and on a lazily-loaded list it will trigger loading. Leave it off when the app must not be disturbed."
  3. Changed2 schema fields changed
    • changedInput schema / properties / checks / description
      Previous value: -"Checks to run; omit for all. \"TouchTargetSize\" = tap targets below the recommended minimum; \"DuplicateClickableBounds\" = several tappable elements on identical bounds; \"MissingClickAction\" = a button-class element exposing no click action; \"RedundantDescription\" = description restates type/state/action; \"ClassName\" = control reports an uninterpretable class."New value: +"Checks to run; omit for all. \"TouchTargetSize\" = tap targets below the recommended minimum; \"DuplicateClickableBounds\" = several tappable elements on identical bounds; \"MissingClickAction\" = a button-class element exposing no click action; \"SpeakableTextPresent\" = an actionable control with no text, content description or labelled descendant; \"RedundantDescription\" = description restates type/state/action; \"ClassName\" = control reports an uninterpretable class."
    • changedInput schema / properties / checks / items / enum
      Previous value: -[
      -  "TouchTargetSize",
      -  "DuplicateClickableBounds",
      -  "MissingClickAction",
      -  "RedundantDescription",
      -  "ClassName"
      -]New value: +[
      +  "TouchTargetSize",
      +  "DuplicateClickableBounds",
      +  "MissingClickAction",
      +  "SpeakableTextPresent",
      +  "RedundantDescription",
      +  "ClassName"
      +]
  4. Changed4 schema fields changed
    • changedInput schema / properties / checks / description
      Previous value: -"Checks to run; omit for all. \"TouchTargetSize\" = tap targets below the recommended minimum; \"DuplicateClickableBounds\" = several tappable elements on identical bounds; \"RedundantDescription\" = description restates type/state/action; \"ClassName\" = control reports an uninterpretable class."New value: +"Checks to run; omit for all. \"TouchTargetSize\" = tap targets below the recommended minimum; \"DuplicateClickableBounds\" = several tappable elements on identical bounds; \"MissingClickAction\" = a button-class element exposing no click action; \"RedundantDescription\" = description restates type/state/action; \"ClassName\" = control reports an uninterpretable class."
    • changedInput schema / properties / checks / items / enum
      Previous value: -[
      -  "TouchTargetSize",
      -  "DuplicateClickableBounds",
      -  "RedundantDescription",
      -  "ClassName"
      -]New value: +[
      +  "TouchTargetSize",
      +  "DuplicateClickableBounds",
      +  "MissingClickAction",
      +  "RedundantDescription",
      +  "ClassName"
      +]
    • addedInput schema / properties / maxScrollSteps
      Added value: +{
      +  "description": "Only with scroll:true. Maximum scrolls before stopping regardless (default 6, max 20).",
      +  "maximum": 20,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / scroll
      Added value: +{
      +  "description": "Defaults false. When true, audit the screen, scroll down, and audit again — repeating until a pass reveals no new elements or maxScrollSteps is reached — then report the deduplicated union. This CHANGES THE SCREEN: it scrolls the app and does not scroll back, and on a lazily-loaded list it will trigger loading. Leave it off when the app must not be disturbed.",
      +  "type": "boolean"
      +}
  5. Added

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so exceptionally. It openly states that results are 'a screening signal, not a verdict,' documents that only on-screen elements are examined, explains the ancestor-touch-dispatch blind spot, and discloses that scroll mode changes the screen (further detailed in the schema). It also explains WHY contrast/text-size are excluded, which lets the agent set correct expectations.

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?

The description is long but well-structured and front-loaded: purpose first, then checks, then usage, then a clearly marked 'IMPORTANT LIMITS' section. The prose list of the six checks partially duplicates the schema's enum descriptions, which is a slight inefficiency, but every other sentence earns its place by adding operational or interpretive value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 5 parameters and no output schema, the description is remarkably complete. It explains prerequisites, the full scope of what is audited, what is deliberately not audited and why, how the scroll mode behaves, and — critically — what findings carry ('label, class and pixel rect') so the agent can act on results despite the absent output schema.

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 the baseline is 3. The description's prose enumeration of the six checks largely restates what the schema's enum descriptions already provide, and it adds nothing beyond the schema for udid, scroll, maxScrollSteps, or localeIsEnglish. The one modest addition is the note that each finding's rect centre is tappable, but that concerns output, not parameters.

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?

The opening sentence states a specific verb and resource: 'Run an accessibility audit on the CURRENT screen of an Android device.' The platform and scope are explicit, which distinguishes it from the sibling ios_accessibility_audit even without opening the schema. The subsequent enumeration of the six checks gives the agent a concrete sense of what the audit produces.

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?

The description gives explicit sequencing guidance: 'navigate to the screen you care about FIRST (device_tap_by_text / device_launch_app), then call this.' It also states when to pass scroll:true and explicitly lists exclusions ('Contrast and text-size are NOT checked'). It does not name an alternative tool for exclusion, but the platform and workflow context are clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources