Skip to main content
Glama
rahulkr
by rahulkr

press_home

Press the home button on an Android device to return to the home screen or exit apps during development, testing, or debugging workflows.

Instructions

Press the home button

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_serialNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'press_home' tool. Decorated with @mcp.tool() for registration in FastMCP. Implements pressing the Android HOME key by calling the press_key helper function.
    @mcp.tool()
    def press_home(device_serial: str | None = None) -> str:
        """Press the home button"""
        return press_key("HOME", device_serial)
  • Supporting helper function 'press_key' that maps string keycodes like 'HOME' to numeric codes (e.g., '3') and executes the ADB command to simulate key press. Directly called by press_home.
    @mcp.tool()
    def press_key(keycode: str, device_serial: str | None = None) -> str:
        """
        Press a key by keycode name or number.
        
        Common keycodes:
        - HOME (3), BACK (4), CALL (5), ENDCALL (6)
        - VOLUME_UP (24), VOLUME_DOWN (25), POWER (26)
        - CAMERA (27), ENTER (66), DEL/BACKSPACE (67)
        - TAB (61), SPACE (62), MENU (82)
        - SEARCH (84), MEDIA_PLAY_PAUSE (85)
        - PAGE_UP (92), PAGE_DOWN (93)
        """
        # Handle common names
        key_map = {
            'HOME': '3', 'BACK': '4', 'ENTER': '66', 'DELETE': '67', 'DEL': '67',
            'TAB': '61', 'SPACE': '62', 'MENU': '82', 'SEARCH': '84',
            'VOLUME_UP': '24', 'VOLUME_DOWN': '25', 'POWER': '26',
            'PAGE_UP': '92', 'PAGE_DOWN': '93', 'ESCAPE': '111', 'ESC': '111'
        }
        
        key = key_map.get(keycode.upper(), keycode)
        return run_adb(["shell", "input", "keyevent", key], device_serial)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('Press the home button') without mentioning effects (e.g., returning to home screen, potential app state changes), permissions required, or any side effects like rate limits or device-specific behaviors.

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, direct sentence ('Press the home button') with no wasted words, making it highly concise and front-loaded. Every word earns its place by clearly stating the tool's action.

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?

Given the tool's low complexity (simple action with one optional parameter) and the presence of an output schema (which handles return values), the description is minimally adequate. However, it lacks context on usage scenarios and behavioral details, which are needed for full completeness, especially with no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one parameter (device_serial) with 0% description coverage, and the description doesn't mention parameters at all. However, since there's only one optional parameter, the baseline is high. The description doesn't add meaning beyond the schema, but the minimal parameter count keeps the score from dropping lower.

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 'Press the home button' clearly states the action (press) and target (home button), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'press_back' or 'press_recent_apps' beyond the button name, which keeps it from a perfect score.

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 offers no guidance on when to use this tool versus alternatives like 'press_back' or 'press_recent_apps', nor does it mention any prerequisites or context for usage. It merely states what the tool does without indicating appropriate scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rahulkr/r_adb_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server