Skip to main content
Glama

adb_reboot

Reboot an Android device into normal, recovery, or bootloader mode, optionally targeting a specific device by serial.

Instructions

Reboot the device. Supports normal, recovery, and bootloader modes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adb_reboot"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoReboot mode: normal (default), recovery, or bootloadernormal
deviceNoDevice serial

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

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. Although "Reboot" signals a disruptive state change, it omits temporary device and ADB unavailability, possible disconnection or reconnection requirements, and mode-specific consequences.

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?

Two short sentences front-load the operation and immediately state the supported modes. There is no redundant or unnecessary wording.

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 simple two-parameter tool, the stated operation and fully documented schema support basic selection and invocation. However, the missing availability, disconnection, and boot-readiness guidance is consequential for a reboot tool with no annotations or output schema.

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 coverage is 100%, with the mode enum and default and the device serial already documented. The description repeats the supported modes but adds no targeting or invocation semantics beyond the schema, so it meets the baseline without adding further value.

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—"Reboot the device"—and the mode list clarifies its scope. It does not explicitly contrast this whole-device operation with siblings such as adb_restart_app, though no sibling appears to duplicate its function.

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?

Listing normal, recovery, and bootloader modes describes capability rather than when to use the tool or how to choose a mode. There are no prerequisites, exclusions, or follow-up recommendations such as waiting for the device to boot or reconnecting.

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