Skip to main content
Glama

adb_device_state

Retrieve a combined Android device state snapshot—battery, network, screen, foreground activity, and orientation—in one call for UI automation pre-checks or quick health checks.

Instructions

Get a combined device state snapshot in one call: battery level/status, network connectivity, screen on/off, foreground activity, and orientation. Useful as a pre-check before UI automation or as a quick device health summary.

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_device_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Get ... snapshot" establishes a read-only, point-in-time operation, but the description does not state prerequisites (e.g., an attached/authorized device), what happens when `device` is omitted and multiple devices are connected, or whether the call is fast/rate-limited. For a no-annotation read tool that is adequate but thin.

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 sentences, zero filler: the first front-loads the action and lists the returned components; the second gives the use case. Every clause earns its place and nothing is repeated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully acts as a return-value sketch by enumerating the five state components, which is what an agent needs to know before deciding to call it. The remaining gap is only the no-annotation behavioral detail (device resolution, failure modes), which is minor for a read-only snapshot tool.

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?

Only one parameter (`device`, "Device serial") with 100% schema description coverage, so the schema already documents it fully. The description adds no meaning about device selection or default behavior when the parameter is omitted, which is the one ambiguity that matters given required=0. Baseline 3 is appropriate.

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?

"Get a combined device state snapshot in one call" gives a specific verb plus an aggregation resource, and the description enumerates exactly what is bundled: battery level/status, network connectivity, screen on/off, foreground activity, orientation. The phrase "in one call" implicitly distinguishes it from the granular siblings (adb_battery, adb_network, adb_screen_state, adb_current_activity, adb_orientation), though it never names them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Useful as a pre-check before UI automation or as a quick device health summary" gives two concrete usage contexts, which is more than most definitions offer. It stops short of explicit routing advice such as "use adb_battery when you only need battery detail" or an exclusion against adb_health_check/adb_device_info, so the agent must infer the aggregation-vs-single-metric tradeoff.

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