Skip to main content
Glama

swipe

Execute swipe gestures on Android devices to navigate interfaces or scroll content using directional inputs and customizable timing.

Instructions

Perform a swipe gesture in a specific direction on the connected Android device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directionYes
durationNo

Implementation Reference

  • The main handler function for the 'swipe' tool, decorated with @mcp.tool() for automatic registration. It performs swipe gestures on an Android device using ADB's input swipe command based on direction (up, down, left, right) and duration.
    @mcp.tool()
    def swipe(direction: str, duration: int = 500) -> str:
        """Perform a swipe gesture in a specific direction on the connected Android device"""
        directions = {
            "up": (500, 1500, 500, 500),
            "down": (500, 500, 500, 1500),
            "left": (1500, 500, 500, 500),
            "right": (500, 500, 1500, 500),
        }
        if direction not in directions:
            raise ValueError(
                f"Invalid direction '{direction}'. Valid directions are: {list(directions.keys())}"
            )
    
        start_x, start_y, end_x, end_y = directions[direction]
        result = subprocess.run(
            [
                "adb",
                "shell",
                "input",
                "swipe",
                str(start_x),
                str(start_y),
                str(end_x),
                str(end_y),
                str(duration),
            ],
            capture_output=True,
            text=True,
        )
        if result.returncode != 0:
            raise RuntimeError(f"Error performing swipe: {result.stderr}")
        return f"Swipe gesture performed in '{direction}' direction over {duration}ms."
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('perform a swipe gesture') but doesn't clarify behavioral aspects such as whether this requires specific device states (e.g., unlocked screen), what happens if the swipe fails, or if there are rate limits or side effects. This is inadequate for a mutation tool with zero annotation coverage.

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 and context without any wasted words. It's appropriately sized for a simple tool, making it easy for an agent to parse quickly.

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 the tool's complexity (a mutation action on a device with 2 parameters), lack of annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't explain parameter details, behavioral constraints, or what to expect upon execution, leaving significant gaps for the agent to operate safely and 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 by explaining parameters. It mentions 'direction' implicitly ('in a specific direction') but doesn't define valid values (e.g., up, down, left, right) or units. It doesn't mention the 'duration' parameter at all, leaving it undocumented. This fails to add meaningful semantics beyond the bare schema.

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 ('perform a swipe gesture') and the target ('on the connected Android device'), which is specific and unambiguous. However, it doesn't differentiate this tool from sibling tools like 'tap' or 'press_button', which are also gesture/input tools for Android devices, leaving some ambiguity about when to choose swipe over those alternatives.

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 'tap' or 'press_button'. It mentions the context ('connected Android device') but gives no explicit when/when-not instructions or comparisons to sibling tools, leaving the agent to infer usage based on the tool name alone.

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