Skip to main content
Glama

tap

Simulate screen taps on Android devices by specifying X and Y coordinates for automated testing or remote control.

Instructions

Simulate a tap on the connected Android device at the specified coordinates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYes
yYes

Implementation Reference

  • The main handler function for the 'tap' tool. It uses adb to simulate a tap gesture at given coordinates (x,y) on the connected Android device/emulator. Includes error handling and success message.
    @mcp.tool()
    def tap(x: int, y: int) -> str:
        """Simulate a tap on the connected Android device at the specified coordinates"""
        result = subprocess.run(
            ["adb", "shell", "input", "tap", str(x), str(y)],
            capture_output=True,
            text=True,
        )
        if result.returncode != 0:
            raise RuntimeError(f"Error performing tap at ({x}, {y}): {result.stderr}")
        return f"Tap performed at coordinates ({x}, {y})."
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'simulate a tap' which implies a UI interaction, but doesn't disclose behavioral traits like whether it requires device connectivity, potential side effects (e.g., app navigation), error handling, or response format. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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?

The description is a single, efficient sentence that front-loads the core action ('simulate a tap') and context ('on the connected Android device'). There is no wasted text, and it directly conveys the purpose without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and low schema description coverage (0%), the description is incomplete. It lacks details on prerequisites (e.g., device state), behavioral outcomes, error cases, and parameter specifics. For a tool with 2 required parameters and no structured support, the description should provide more context to be fully helpful.

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?

The description adds meaning by specifying that coordinates are for 'tap' simulation, but the input schema has 0% description coverage (no schema descriptions for x and y). The description doesn't explain coordinate systems (e.g., screen pixels, relative units), valid ranges, or units. It partially compensates by linking parameters to the action, but doesn't fully address the coverage gap.

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 clearly states the action ('simulate a tap') and the target ('on the connected Android device'), with specific coordinates as parameters. It distinguishes from siblings like 'swipe' or 'press_button' by focusing on a single tap action. However, it doesn't explicitly differentiate from all siblings (e.g., 'type_text' is clearly different, but the distinction could be more explicit for some).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., device must be connected), exclusions (e.g., not for long presses), or sibling tools like 'swipe' for gestures. Usage is implied by the action but lacks explicit context.

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/vs4vijay/espresso-mcp'

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