Skip to main content
Glama
rahulkr

Enhanced ADB MCP Server

by rahulkr
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

reboot_device

Restart Android devices in normal, bootloader, or recovery modes for development, testing, and debugging workflows.

Instructions

Reboot the device.
mode: 'normal', 'bootloader', 'recovery'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNonormal
device_serialNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/adb_mcp_server/server.py:997-1007 (handler)
    The handler function for the 'reboot_device' tool. Decorated with @mcp.tool() which handles registration in FastMCP. Executes ADB reboot commands based on the mode: normal, bootloader, or recovery. Returns the output from run_adb or an error message for invalid mode.
    def reboot_device(mode: str = "normal", device_serial: str | None = None) -> str:
    """
    Reboot the device.
    mode: 'normal', 'bootloader', 'recovery'
    """
    if mode == "normal":
        return run_adb(["reboot"], device_serial)
    elif mode in ["bootloader", "recovery"]:
        return run_adb(["reboot", mode], device_serial)
    return "Invalid mode. Use: normal, bootloader, recovery"

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Reboot' implies a potentially disruptive operation, the description doesn't warn about device downtime, data loss risks, or permission requirements. The mode parameter values hint at different reboot behaviors but aren't explained.

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 extremely brief with just two lines, front-loading the core purpose. However, the second line about mode values feels tacked on without proper integration, slightly disrupting flow. Every word serves a purpose, but more structure could improve clarity.

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?

For a potentially destructive operation with 2 parameters and no annotations, the description is inadequate. While an output schema exists, the description doesn't address critical behavioral aspects like disruption level, success indicators, or error conditions. The parameter documentation is incomplete, and there's no safety guidance.

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 0%, so the description must compensate. It provides mode parameter values ('normal', 'bootloader', 'recovery') which add meaningful context beyond the schema's generic string type. However, it doesn't explain what these modes do or mention the device_serial parameter at all, leaving half the parameters undocumented.

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 clearly states the action ('Reboot') and resource ('the device'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other device control tools like 'toggle_wifi' or 'rotate_screen' beyond the specific reboot action.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites like device connectivity or state requirements. There's no indication of when rebooting is appropriate versus other troubleshooting tools like 'clear_app_data' or 'force_stop_app'.

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