Skip to main content
Glama

android_swipe

Destructive

Swipe or scroll on an authorized Android phone by sending start and end display coordinates, with optional device targeting and swipe duration.

Instructions

Swipe or scroll between display 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": {
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>"
    },
    "name": "android_swipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1Yes
x2Yes
y1Yes
y2Yes
deviceNoOptional connected device id, connection serial or exact model. Overrides the selected/default phone for this call.
durationMsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.3

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not warn that a swipe can trigger irreversible actions (dismissing items, drag-and-drop, pull-to-refresh), nor explain that durationMs changes the gesture from a fling to a controlled drag. This is a meaningful gap for a destructive gesture tool.

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?

A single short sentence with no filler, and the action verb is front-loaded. It is efficient, but the brevity comes at the cost of the missing detail noted elsewhere rather than being a model of tight-yet-complete phrasing.

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?

Six parameters, 17% schema coverage, no output schema, and destructive annotations – this tool needs substantially more explanation than one line. Nothing tells the agent the coordinate pairing convention, gesture duration effects, or the risk of unintended UI side effects.

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 only 17% – just the device override is documented in the schema. The description supplies no meaning for x1/y1/x2/y2 (start vs end point, coordinate origin, 0–20000 bounds) and none for durationMs (default 350, max 5000, and how it affects gesture speed). With low coverage the description should compensate, and it does not.

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

Purpose3/5

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

"Swipe or scroll between display coordinates" names a concrete gesture action, so the agent knows this is a drag-style interaction rather than a tap. However, it never clarifies that the four coordinates form a start point (x1,y1) and an end point (x2,y2), nor what direction of scroll is produced. The purpose is recognizable but underspecified.

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?

There is no guidance on when to use this instead of android_tap or android_tap_element, no mention of needing a prior device selection despite the device override parameter, and no discussion of when a long/slow swipe (high durationMs) versus a short fling is appropriate. The agent must infer all routing decisions.

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