Skip to main content
Glama

adb_input_double_tap

Performs a double tap at specified screen coordinates to trigger zoom, text selection, or other double-tap gestures, with a configurable interval between taps.

Instructions

Double tap at a point on screen. Triggers zoom, text selection, or double-tap gestures. Two rapid taps with a configurable interval.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "adb_input_double_tap"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX coordinate
yYesY coordinate
deviceNoDevice serial
intervalMsNoInterval between taps in ms (20-500, default 80)

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.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses that two rapid taps are issued with a configurable interval and what UI behaviors that can trigger, but says nothing about required device connectivity, whether coordinate bounds outside the screen are clamped, or any side effects on app state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and effect, with zero filler. Every clause contributes either the operation, its outcome, or the tap timing.

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 simple four-parameter input-injection tool with a fully documented schema and no output schema, the description covers the action, trigger behaviors, and timing semantics adequately. Only device/coordinate edge-case behavior is left implicit.

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%, with x, y, device, and intervalMs documented including range and default, so the schema does the heavy lifting. The description's mention of 'a configurable interval' restates intervalMs without adding meaning beyond the schema baseline.

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 names a specific verb and resource ('Double tap at a point on screen') and explains the resulting effect ('Triggers zoom, text selection, or double-tap gestures'). It is clearly distinguishable from gesture siblings like adb_input_long_press or adb_input_drag by implication, though it never names them explicitly.

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?

Usage is only implied: an agent can infer this is for double-tap interactions (zoom, text selection), but there is no explicit when-to-use/when-not or routing to alternatives such as adb_input, adb_tap_element, or adb_input_long_press. A brief 'use instead of two adb_input taps' note would have closed the gap.

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