Skip to main content
Glama

adb_screen_state

Capture a combined Android screen snapshot—foreground activity, dimensions, orientation, battery, and interactive UI elements—in one call to replace multiple ADB queries.

Instructions

Get a combined screen state snapshot in one call: foreground activity, screen dimensions and density, orientation, battery level, and a TSV list of interactive UI elements. Replaces 3-4 separate tool calls with a single round-trip. Ideal as a first step in any automation workflow.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
clickableOnlyNoOnly include clickable/scrollable elements in TSV output (default true)

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

A4/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 burden. It discloses the returned contents and a performance trait (one round-trip instead of 3-4), but never states that it is a read-only/non-mutating operation, whether the UI dump has side effects or latency cost, or whether it requires the device to be booted and authorized.

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?

Three sentences, front-loaded with the payload, then the efficiency rationale, then the workflow placement. Nothing is redundant and each sentence adds a distinct decision-relevant fact.

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?

There is no output schema, so the description must describe return values and it does so by enumerating every component of the snapshot. The remaining gap is behavioral rather than structural: safety, prerequisites, and latency for an unannotated tool are left implicit.

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 100%, so both parameters (device, clickableOnly) are already documented in structured form; baseline 3 applies. The description hints at the clickableOnly effect by describing the output as a list of 'interactive UI elements', but adds no format or behavior detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ('Get') plus an enumerated payload: foreground activity, dimensions/density, orientation, battery level, and a TSV element list. This clearly distinguishes it from the granular siblings it aggregates (adb_current_activity, adb_screen_size, adb_ui_dump, adb_battery) without requiring the schema to be opened.

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?

'Replaces 3-4 separate tool calls with a single round-trip' and 'Ideal as a first step in any automation workflow' give a clear selection context versus the single-purpose siblings. However, it never names those siblings explicitly nor states when NOT to use it (e.g. when only one datum is needed, or when a full UI dump is required).

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