Skip to main content
Glama

Robot Actions — Remote Device Control

by com.robotactions.test
OverviewDiscussionsAdmin

Android accessibility audit

android_accessibility_audit
Read-onlyIdempotent

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, so summary.actionableNodes counts the tappable elements (clickable rows included) currently on screen, not the whole list; 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.8/5.0
Behavior5/5

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

Annotations give readOnlyHint/idempotentHint/destructiveHint, but the description adds context they cannot: scroll:true 'CHANGES THE SCREEN: it scrolls the app and does not scroll back' and triggers lazy loading. It also discloses the important non-obvious limits (tap-target screening is a signal not a verdict, only on-screen drawn elements examined, ancestor-driven tappability invisible, contrast/text-size NOT checked).

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?

Dense but front-loaded: purpose first, then fold/scroll guidance, then finding types, then limits. Every sentence carries information (finding semantics, rect-as-tap-point, caveats), though the block is long enough that an agent may need to scan rather than read once.

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?

No output schema exists, yet the description covers the return shape (each finding carries label, class and pixel rect; rect centre is tappable via device_tap) and the aggregate caveat about summary.actionableNodes. Combined with the disclosed limits, an agent has everything needed to call and interpret it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description still adds real value, explaining why localeIsEnglish exists (English word matching for the redundant-description check), what maxScrollSteps bounds, and the side effects of scroll:true. It goes beyond restating the schema, though per-parameter coverage is already strong.

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 with scope: 'Run an accessibility audit on the CURRENT screen of an Android device'. It also positions itself against the iOS sibling implicitly via platform and explains the rule basis (Google Accessibility Scanner). An agent can distinguish this from ios_accessibility_audit and device_page_source 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit sequencing: 'navigate to the screen you care about FIRST (device_tap_by_text / device_launch_app), then call this', plus a named alternative behavior for scroll:true and a when-not-to condition ('Leave it off when the app must not be disturbed'). Nothing is left to inference.

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

All Robot Actions — Remote Device Control toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources