Skip to main content
Glama
Sign In
android-mcp

android-mcp

by AsmanovLev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

mobile_power

Manage Android device power state by turning the screen on or off, checking if awake, or rebooting.

Instructions

Control device power state: turn screen on/off, check if awake, or reboot.

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": "mobile_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesPower action
serialNoADB device serial (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral disclosure burden. It conveys that 'reboot' is a destructive action and 'awake' is a check, but lacks details such as whether rebooting causes temporary unavailability or if screen on/off requires secure unlock.

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?

Single sentence, efficiently front-loaded with the purpose and actions. No unnecessary words or structure issues.

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 simplicity (2 params, no output schema), the description is adequate but incomplete. It omits information about return values (e.g., what 'awake' returns) and potential side effects of reboot, which would help an agent handle the response correctly.

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%, so baseline is 3. The description adds no extra meaning to parameters beyond the schema's enum values and optional serial description; it merely mirrors them.

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 tool controls device power state and lists specific actions (turn screen on/off, check awake, reboot). This distinguishes it from sibling tools like mobile_screenshot or mobile_state, which handle different aspects of device interaction.

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?

No guidance on when to use this tool versus alternatives. For instance, it does not explain when to use 'reboot' versus 'on'/'off', or how this relates to other mobile tools like mobile_button (which might also affect screen state).

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