Skip to main content
Glama

Robot Actions — Remote Device Control

by com.robotactions.test
OverviewDiscussionsAdmin

Android TalkBack

android_talkback

Drive Android's TalkBack screen reader and read what it is focused on. Actions: 'status' (is it on, and what is focused), 'enable' / 'disable' (turn TalkBack on or off — up to ~5 s; 'start' / 'stop' are accepted as the same, matching ios_voiceover), 'next' / 'previous' (swipe to the next or previous item, as a TalkBack user would), 'activate' (double-tap the focused item). Returns code, enabled, running, text, className and the focused item's bounds in screen pixels. text is COMPOSED from the focused node (its label, role and state, plus any announcement made during the action) — close to what TalkBack says but not its verbatim spoken string: usage hints and exact word order are not included. Each action takes up to ~3 s. code 'not_running' means TalkBack is off and the gesture was NOT sent — enable it first. code 'text_unavailable' means another UI-automation client (such as a running test session) holds the device: the gesture was still performed but no text could be read. code 'not_installed' means the device has no TalkBack. While TalkBack is on, ordinary taps and swipes behave differently (a single tap only moves focus), so disable it when done. The device is kept silent automatically while TalkBack is on, unless someone is watching it in a browser, who hears it instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
udidYesDevice serial number (UDID)
actionYesWhat to do. 'status' changes nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "status",
-  "enable",
-  "disable",
-  "next",
-  "previous",
-  "activate"
-]New value: +[
+  "status",
+  "enable",
+  "disable",
+  "start",
+  "stop",
+  "next",
+  "previous",
+  "activate"
+]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Far exceeds the annotations (readOnlyHint false, destructiveHint false, idempotentHint false): discloses ~5 s enable/disable latency, ~3 s per action, the meaning of code values ('not_running', 'text_unavailable', 'not_installed'), the side effect that single taps only move focus while TalkBack is on, and the automatic silence/local-versus-remote audio behavior — none of which the annotations convey.

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?

Front-loads purpose and the action catalog, then error codes and side effects; every sentence carries information. It is long and dense, but the length is justified by the multi-action surface and the important error/side-effect caveats.

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, and the description fully documents the return fields (code, enabled, running, text, className, bounds) plus the caveat that 'text' is composed rather than verbatim spoken output. Nothing an agent needs to invoke or interpret the tool correctly is missing.

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% and the enum already lists the action values, so the baseline is 3; the description nonetheless adds real meaning by explaining what each action does (gesture semantics for next/previous, double-tap for activate) and clarifying 'status' is a no-op. It does not add format detail for udid beyond the schema, so it is not a full 5.

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 (Drive) and resource (Android's TalkBack screen reader) and enumerates every action with its meaning, so an agent can match intent without opening the schema. It is clearly distinguishable from siblings like android_accessibility_audit and pairs the alias 'start'/'stop' with ios_voiceover.

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?

Gives clear operational conditions: enable TalkBack first when code is 'not_running', disable it when done because taps/swipes change behavior, and notes 'status' changes nothing. It does not explicitly contrast with alternative accessibility tools, so it stops short of naming when-not-to-use alternatives.

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
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources