Skip to main content
Glama
Sign In
adb-ai

adb-ai

by cyberpunk2183
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

adb_power

Controls Android device power state by putting the screen to sleep or waking it over ADB.

Instructions

Put the screen to sleep or wake the device.

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": {
      "action": "<action>"
    },
    "name": "adb_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
deviceNoserial, ip[:port] or saved alias; omit to use the default device

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says what the tool does at a high level, but does not explain side effects, required permissions, whether sleep turns off the display only, or what happens to running apps.

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 front-loaded sentence with no wasted words. However, it is so terse that it omits useful context, so it is efficient rather than fully well-structured for an unannotated tool.

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 with no output schema, the description is minimally adequate: the action is clear and the device parameter is covered by the schema. Still, given the absence of annotations, it should say more about behavior and prerequisites.

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

Parameters2/5

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

Schema coverage is only 50%, and the description adds little beyond restating the sleep/wake action values already encoded in the enum. The device parameter is documented in the schema but is not mentioned in the description, so it does not compensate for the coverage gap.

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 states a specific operation: putting the screen to sleep or waking the device. That is clear enough to distinguish it from siblings like adb_state or adb_screenshot, but it does not explicitly name or differentiate against those alternatives.

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 such as adb_state or adb_key. The action enum implies the two modes, but there are no explicit use cases, prerequisites, or exclusions.

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