Skip to main content
Glama
Sign In
android-mcp

android-mcp

by AsmanovLev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

mobile_button

Press Android hardware buttons (back, home, recent, menu, volume, power, camera, call) via ADB for device control and automation.

Instructions

Press a hardware/system button on the Android device: back, home, recent apps, menu, volume up/down, power, camera, or call.

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": {
      "button": "<button>"
    },
    "name": "mobile_button"
  }
}

Input Schema

NameRequiredDescriptionDefault
buttonYesButton to press
serialNoADB device serial (optional)
return_screenNoCapture screen after button press (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It states it presses a button but does not mention side effects (e.g., screen capture via return_screen) or prerequisites (e.g., ADB connection). The description could be more explicit about behavior.

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 sentence that front-loads the action and lists all relevant buttons. No wasted words and clearly structured.

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 tool with no output schema and high schema coverage, the description is fairly complete. It covers the core action and button options. However, it could mention the default screen capture behavior and the optional serial parameter for multi-device contexts.

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 redundancy by listing buttons, but does not provide additional meaning for serial or return_screen beyond what the schema already describes.

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 ('Press a hardware/system button') and lists the specific buttons (back, home, recent, etc.). This distinguishes it from sibling tools like mobile_gesture (touch gestures) and mobile_power (power management).

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 usage for pressing hardware buttons but does not explicitly state when to use this tool versus alternatives like mobile_gesture or mobile_power. No when-not or alternative guidance is provided.

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