Skip to main content
Glama
Sign In
android-mcp

android-mcp

by AsmanovLev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

mobile_gesture_macro

Execute predefined gesture macros for common Android actions: unlock, home, back, recents, notification panel, and quick settings. Control device via ADB with optional screenshot capture.

Instructions

Execute a named gesture macro (e.g., 'unlock', 'home', 'back', 'recents', 'notification_panel', 'quick_settings').

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": {
      "macro": "<macro>"
    },
    "name": "mobile_gesture_macro"
  }
}

Input Schema

NameRequiredDescriptionDefault
macroYesMacro name
serialNoADB device serial (optional)
return_screenNoCapture screen after macro (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only says 'Execute', without mentioning blocking behavior, failure handling, prerequisites, or side effects beyond what is implicit from the macro name.

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?

The description is a single efficient sentence with examples. It is front-loaded and appropriately sized, though the examples are slightly redundant with the enum.

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?

Given no output schema, no annotations, and the tool's side-effect nature (macro execution), the description is incomplete. It lacks information about return values, prerequisites, and how it relates to sibling tools like mobile_gesture_combo.

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 no further meaning; it merely lists examples already covered by the enum. It does not enrich understanding of 'serial' or 'return_screen' beyond their schema descriptions.

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 ('Execute') and the resource ('named gesture macro') with concrete examples, distinguishing it from siblings like mobile_gesture (single gestures) and mobile_gesture_combo (combo gestures).

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?

The description does not provide any guidance on when to use this tool vs alternatives (e.g., mobile_gesture, mobile_gesture_combo). No when-not-to-use or exclusion criteria are given.

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