android-mcp

by mii-shell

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

swipe

Simulates a touch gesture from one screen point to another; set duration ≥1000ms to perform a drag.

Instructions

Swipe/drag from one screen point to another. A slow swipe (duration >= 1000) acts like a drag.

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": {
      "from_x": "<from_x>",
      "from_y": "<from_y>",
      "to_x": "<to_x>",
      "to_y": "<to_y>"
    },
    "name": "swipe"
  }
}

Input Schema

Name	Required	Description	Default
`to_x`	Yes
`to_y`	Yes
`from_x`	Yes
`from_y`	Yes
`serial`	No	adb serial; optional when exactly one device is connected
`observe`	No	What to return after the action: changes (default: only what changed since you last saw the screen, full tree on a new screen), ui (full tree), screenshot, both (tree + screenshot), none	changes
`settle_ms`	No	Wait before observing
`duration_ms`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that slow swipes act as drags, but it does not state that this mutates UI state, requires a connected device, or that behavior may depend on the observe parameter.

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?

Two short sentences, front-loaded with the core action and followed by the one non-obvious behavioral caveat. There is no wasted text.

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?

For an 8-parameter UI gesture tool with no annotations and no output schema, the description is thin. The observe parameter's schema documentation covers return behavior, but the description should still mention coordinate assumptions and device requirements.

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 coverage is only 38%, but the description adds a key semantic detail not present in the schema: duration >= 1000 changes the gesture into a drag. It does not clarify coordinate space, screen-relative units, or how from/to points interact with device resolution.

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 states a specific verb and resource: 'Swipe/drag from one screen point to another.' It is clearly a gesture tool, but it never names or differentiates itself from siblings such as tap, long_press, or scroll, leaving the agent to infer the boundary.

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

Usage Guidelines3/5

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

The drag threshold ('duration >= 1000') gives useful implied usage guidance for turning a swipe into a drag. However, there is no explicit when-to-use guidance versus tap, long_press, or scroll, and no prerequisites or exclusions are stated.

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