Skip to main content
Glama
Sign In
run-sequence-android-mcp

run-sequence-android-mcp

by nasiosheva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Swipe Screen

android_swipe

Swipe an Android device screen in a chosen direction from the center or custom X/Y coordinates to navigate apps, menus, and gestures.

Instructions

Swipe in a direction. Starts from screen center by default, or from given x,y coordinates.

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": {
      "direction": "<direction>"
    },
    "name": "android_swipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoStart X coordinate. Defaults to screen center.
yNoStart Y coordinate. Defaults to screen center.
deviceNoDevice id (serial or host:port). Optional -- when omitted, uses ANDROID_MCP_DEVICE env or auto-selects the connected device (physical devices preferred over emulators).
distanceNoSwipe distance in pixels. Defaults to ~55% of screen for center swipes, 30% for coordinate swipes.
durationNoSwipe duration in milliseconds. Defaults to 500.
directionYesSwipe direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations are empty, so description must disclose all behavioral traits. It mentions start location defaults but omits effects of duration, distance, or that it is a touch gesture with release. Incomplete for safe agent use.

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?

Single sentence, direct and to the point. No wasted words, but could be expanded without losing conciseness.

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?

With 6 parameters and no output schema, the description is too sparse. It doesn't explain how parameters interact (e.g., distance vs duration) or what the swipe looks like, leaving gaps for effective use.

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%, so baseline is 3. The description adds minimal new meaning (start location defaults already in schema). No improvement over 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 tool swipes on a screen, starting from center or given coordinates. It distinguishes from siblings like tap or long press by focusing on directional motion, but doesn't explicitly contrast with drag.

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?

No guidance on when to use swipe versus other gesture tools (drag, tap, etc.). The description lacks context for preferred scenarios or prerequisites.

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