Skip to main content
Glama
rahulkr

Enhanced ADB MCP Server

by rahulkr
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

tap

Simulate screen taps at specified coordinates to interact with Android device interfaces for testing and automation workflows.

Instructions

Tap at screen coordinates (x, y)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYes
yYes
device_serialNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/adb_mcp_server/server.py:393-397 (handler)
    The core handler function for the 'tap' MCP tool. Executes an ADB shell input tap command at the specified screen coordinates (x, y). Supports optional device_serial for multi-device setups.
    @mcp.tool()
def tap(x: int, y: int, device_serial: str | None = None) -> str:
    """Tap at screen coordinates (x, y)"""
    return run_adb(["shell", "input", "tap", str(x), str(y)], device_serial)

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('tap') but doesn't mention what happens after the tap (e.g., UI response, potential app navigation), whether it requires specific device states, or any side effects. This leaves significant behavioral gaps for a UI interaction tool.

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 extremely concise - a single sentence that directly states the tool's function. There's zero wasted language, and it's front-loaded with the essential information. This is an excellent example of efficient communication.

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?

Given that there's an output schema (which handles return values), no annotations, and simple parameters, the description is minimally adequate. However, for a UI interaction tool that likely has important behavioral considerations (timing, device state requirements, visual feedback), the description should provide more context about how and when to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'screen coordinates (x, y)' which helps explain the required x and y parameters, but completely ignores the optional 'device_serial' parameter. This leaves one of three parameters unexplained.

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 ('Tap at') and target ('screen coordinates'), making the purpose immediately understandable. It doesn't distinguish from sibling tools like 'double_tap' or 'tap_element', but it's specific enough to understand the basic function.

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 like 'double_tap', 'long_press', 'tap_element', or 'swipe'. It simply states what the tool does without any context about appropriate use cases or prerequisites.

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/rahulkr/r_adb_mcp_server'

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