@wilsonbeam/openclaw-adb-mcp

by wilsonbeam

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

adb_swipe

Swipe between coordinates on an Android screen. Set start/end points, duration, and device ID for automated gestures.

Instructions

Swipe from one point to another on the screen

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": {
      "startX": "<startX>",
      "startY": "<startY>",
      "endX": "<endX>",
      "endY": "<endY>"
    },
    "name": "adb_swipe"
  }
}

Input Schema

Name	Required	Description
`endX`	Yes	Ending X coordinate
`endY`	Yes	Ending Y coordinate
`startX`	Yes	Starting X coordinate
`startY`	Yes	Starting Y coordinate
`deviceId`	No	Target device ID (optional)
`durationMs`	No	Duration in milliseconds (default 300)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 6, 2026

TDQS

A3.6/5.0

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 only states the basic action and does not mention any side effects, coordinate system details, or that the swipe duration is customizable, though the schema documents the default.

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, concise sentence that front-loads the core purpose. Every word earns its place, with no fluff or repetition.

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

Completeness4/5

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

For a simple gesture tool, the description and schema together are sufficient. The schema fully documents all parameters including the default duration. However, it could mention the coordinate system or that coordinates are screen-relative, but this is a minor gap.

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 the baseline is 3. The description adds no additional meaning beyond what the schema already provides, which is adequate given the schema richness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (swipe) and the resource (screen), with the distinction of moving from one point to another. This differentiates it from sibling tools like adb_tap or adb_long_press.

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 description implies when to use the tool (when a swipe gesture is needed) but does not explicitly state when not to use it or mention alternatives. Given the presence of many sibling input tools, some guidance would be helpful but is not strictly necessary.

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