Android Use

Overview Schema Source Related Servers Discussions Admin

aua_double_tap

Performs a deliberate double tap at a UI selector or screen coordinates, with configurable interval and optional wait/observe, to trigger double-tap actions safely.

Instructions

Perform one intentional pair at selector OR x/y display pixels. interval is seconds between clicks, excluding RPC latency. Supports wait_for and observe. A failed pair may have executed its first click; never replay automatically.

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": "aua_double_tap"
  }
}

Input Schema

Name	Required	Default
`x`	No
`y`	No
`visual`	No
`observe`	No	none
`interval`	No
`selector`	No
`wait_for`	No
`observation_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.6.0Nov 5, 2026

addedInput schema / $defs / LocateArgs

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "description": {
+      "maxLength": 300,
+      "minLength": 1,
+      "title": "Description",
+      "type": "string"
+    },
+    "masks": {
+      "items": {
+        "$ref": "#/$defs/Region"
+      },
+      "maxItems": 8,
+      "title": "Masks",
+      "type": "array"
+    },
+    "min_confidence": {
+      "default": 0.5,
+      "maximum": 1,
+      "minimum": 0,
+      "title": "Min Confidence",
+      "type": "number"
+    },
+    "min_presence": {
+      "default": 0.7,
+      "maximum": 1,
+      "minimum": 0.5,
+      "title": "Min Presence",
+      "type": "number"
+    },
+    "package": {
+      "pattern": "^[a-zA-Z][a-zA-Z0-9_]*(\\.[a-zA-Z0-9_]+)+$",
+      "title": "Package",
+      "type": "string"
+    },
+    "region": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/Region"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    },
+    "timeout_seconds": {
+      "default": 20,
+      "exclusiveMinimum": 0,
+      "maximum": 60,
+      "title": "Timeout Seconds",
+      "type": "number"
+    }
+  },
+  "required": [
+    "package",
+    "description"
+  ],
+  "title": "LocateArgs",
+  "type": "object"
+}

addedInput schema / $defs / Region

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "height": {
+      "exclusiveMinimum": 0,
+      "title": "Height",
+      "type": "integer"
+    },
+    "width": {
+      "exclusiveMinimum": 0,
+      "title": "Width",
+      "type": "integer"
+    },
+    "x": {
+      "minimum": 0,
+      "title": "X",
+      "type": "integer"
+    },
+    "y": {
+      "minimum": 0,
+      "title": "Y",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "x",
+    "y",
+    "width",
+    "height"
+  ],
+  "title": "Region",
+  "type": "object"
+}

addedInput schema / properties / visual

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/LocateArgs"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Addedv0.5.2Nov 5, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the partial-failure hazard ("A failed pair may have executed its first click; never replay automatically") and the precise meaning of interval (seconds between clicks, excluding RPC latency). Annotations only flag non-idempotent/open-world; the description supplies the operational consequence of that non-idempotency, though it doesn't say what a success response looks like.

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, front-loaded with the operation and target mode, followed by the timing caveat and the safety warning in descending priority. No filler, though the first sentence is compressed to the point of being slightly cryptic.

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 non-idempotent, open-world mutation with no output schema, the description correctly covers the irreversible-partial-action risk and the interval semantics. It leaves gaps on the visual locate path, observation_id, and the conflict case between selector and x/y, which matter for an 8-param tool.

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 0% across 8 parameters, so the description must compensate. It explains selector, x/y, interval, wait_for, and observe, but says nothing about visual, observation_id, or what happens if both selector and x/y are supplied.

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?

States a specific verb and resource ("Perform one intentional pair") and pins the target modes (selector OR x/y display pixels), which makes it distinguishable from aua_tap without opening the schema. It stops short of naming the sibling it replaces, so differentiation is implied rather than stated.

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?

The mutual exclusivity of selector vs x/y and the "never replay automatically" rule give implied guidance on how to invoke it, but there is no explicit when-to-use vs aua_tap or aua_long_press, and no stated prerequisites. Usage must be inferred from the operation name.

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