Skip to main content
Glama

gesture-tap

Tap a device screen at normalized coordinates (0-1) for iOS, Android, or Chromium. Supports single tap and double-tap gestures.

Instructions

Press the device screen (iOS simulator, Android emulator, or Chromium app) at normalized coordinates: x and y are fractions of screen width and height in 0.0–1.0 (not pixels). Sends a Down event followed by an Up event at the same point. For Chromium, this dispatches a CDP mouse-press/release on the renderer. Set clickCount: 2 for a double-tap / double-click — the taps are dispatched as one gesture with proper click counting, which two separate tap calls cannot guarantee. Use when you need to tap a button, link, or any tappable element on the screen. Returns { tapped: true, timestampMs }. Fails if the simulator-server / emulator backend / Chromium CDP is not reachable for the given device. Before tapping, determine the correct coordinates by using discovery tools — pick by platform: iOS / Android use describe, native-describe-screen, or debugger-component-tree; Chromium uses describe (the DOM walker), since the native and RN-specific discovery tools don't apply. More information in argent-device-interact skill

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesNormalized horizontal position 0.0–1.0 (left=0, right=1), not pixels
yYesNormalized vertical position 0.0–1.0 (top=0, bottom=1), not pixels
udidYesTarget device id from `list-devices` (iOS UDID, Android serial, or Chromium id).
clickCountNoNumber of taps/clicks dispatched as ONE multi-tap gesture (2 = double-tap / double-click). The taps land inside the OS double-tap window; on Chromium each click carries an escalating CDP clickCount so dblclick actually fires. Default 1.
Behavior5/5

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

With no annotations, the description fully bears the burden. It details the event sequence (Down+Up), platform-specific behavior (CDP for Chromium), double-tap semantics, return value, and failure condition (unreachable backend).

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 informative and well-structured, but slightly lengthy. Each sentence serves a purpose, though some redundancy exists (e.g., repeating 'normalized'). Still clear and efficient.

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?

Despite no output schema, the description mentions the return value and failure conditions. It covers platform-specific details and coordinate discovery, making it complete for a tap tool in this context.

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 adds value by explaining that x,y are fractions (0-1) and clarifying clickCount behavior (single multi-tap gesture vs separate calls). This goes beyond the schema.

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 description clearly states the tool's purpose: pressing the device screen at normalized coordinates. It specifies platforms (iOS, Android, Chromium) and distinguishes from sibling gesture tools (e.g., gesture-drag, gesture-pinch) by focusing on tap/click.

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?

Provides explicit guidance on when to use (to tap buttons, links, etc.) and how to prepare (determine coordinates using discovery tools per platform). Also advises on double-tap vs separate taps, helping the agent choose appropriately.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/software-mansion/argent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server