Skip to main content
Glama

adb_input_fling

Perform rapid fling gestures on Android screens to generate scroll momentum, dismiss notifications, and trigger velocity-sensitive interactions.

Instructions

Perform a high-velocity fling gesture. Like swipe but with a short duration to create scroll momentum on lists, launchers, and paged views. Useful for fast-scrolling through long lists, dismissing notifications, or triggering velocity-sensitive behaviors.

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": "adb_input_fling"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1YesStart X coordinate
x2YesEnd X coordinate
y1YesStart Y coordinate
y2YesEnd Y coordinate
deviceNoDevice serial
durationMsNoFling duration in ms (20-200, default 50). Shorter = more velocity

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does usefully explain the physics of the gesture (short duration produces momentum, useful for velocity-sensitive UI). It says nothing about side effects, that the gesture actually mutates device screen state and can trigger unintended actions, nor anything about permissions or failure modes.

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?

Three tight sentences: the core action first, then the differentiation, then use cases. Every clause carries information and nothing is redundant.

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 a six-parameter gesture-injection tool with no annotations and no output schema, the description covers intent and use cases but omits return behavior, device targeting, and the fact that this performs a real UI action with side effects. It is adequate to call the tool correctly but leaves behavioral gaps an agent would want filled.

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 coordinates, device, and duration are already fully documented, including 'Shorter = more velocity'. The description's talk of high velocity and momentum reinforces but does not add new semantics beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource ('Perform a high-velocity fling gesture') and draws a distinction from the nearest concept ('Like swipe but with a short duration to create scroll momentum'). It does not name any actual sibling tool such as adb_input_drag or adb_input, so the differentiation is conceptual rather than tool-directed.

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

Usage Guidelines4/5

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

It clearly states the contexts where this is the right choice: fast-scrolling long lists, dismissing notifications, and velocity-sensitive behaviors. There is no explicit when-not guidance or a named alternative for cases where a slower drag (adb_input_drag) would be correct, so the routing is implied rather than spelled out.

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