Skip to main content
Glama
Sign In
ADB MCP Server

ADB MCP Server

by LLL-404
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Observe Screen (Screenshot + UI Tree)

adb_observe
Read-only

Take a screenshot and UI hierarchy from an Android device in a single call for examining the current screen layout and content.

Instructions

Take screenshot (base64) + UI tree in one call. Recommended for "looking" at the screen.

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

Input Schema

NameRequiredDescriptionDefault
max_elementsNoMaximum UI elements to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description does not need to repeat these. The description adds that the tool returns both screenshot (base64) and UI tree, which is useful behavioral context. No contradictions with annotations.

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?

The description is a single, efficient sentence that contains all essential information: the tool's action and when to use it. No extraneous words or redundancy.

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?

For a read-only tool with annotations, the description adequately covers the return values (screenshot base64 and UI tree). However, it does not specify the format of the UI tree (likely XML), which could be helpful. Given no output schema, this is a minor gap.

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?

The sole parameter max_elements is fully described in the schema (type, default, min, max). The description does not add any additional meaning beyond what the schema provides. With 100% schema coverage, baseline 3 is appropriate.

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?

The description clearly states the tool captures both screenshot (base64) and UI tree in one call, distinguishing it from sibling tools like adb_screenshot (screenshot only) and adb_ui_tree (UI tree only). The phrase 'Recommended for looking at the screen' reinforces the specific use case.

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?

The description explicitly recommends the tool for 'looking' at the screen, implying it is the preferred choice when both screenshot and UI tree are needed. However, it does not explicitly mention when to use alternatives like adb_screenshot or adb_ui_tree individually, leaving some implicit guidance.

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