Skip to main content
Glama

agentest_connect

Connect to an Android emulator or device and launch the app to get the initial UI screen in compact text format with @ref tokens for use as selectors in subsequent test steps.

Instructions

Connect to an Android emulator/device and launch the app. Returns the initial UI screen in compact text format with @ref tokens you can use as selectors.

The compact format uses one line per element: @b1 btn "Sign in" — button, ref @b1 @f1 input "Email" — text field, ref @f1 @c1 check "Remember me" — checkbox @s1 scroll — scrollable area @l1 link "Forgot?" — clickable text link @g1 tap — generic clickable (unlabeled) "plain text" — non-interactive text

Use refs in subsequent run_flow steps: { "action": "tap", "target": { "ref": "@b1" } } Traditional selectors (id/text/className/description) still work alongside refs.

Pass verbose:true to include framework-sync diagnostics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
backendNoInput backend: "auto" (default) tries gRPC then falls back to ADB; "adb" forces ADB only; "grpc" requires gRPC (emulator only).
verboseNoInclude framework-sync diagnostics in the response.
deviceIdNoSpecific device/emulator ID from "adb devices". Omit to use the first connected device.
packageNameYesAndroid package name (e.g. "com.example.myapp")
Behavior3/5

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

No annotations provided, so description carries full burden. Describes output format (compact text with refs) and optional verbose diagnostics, but does not disclose error scenarios or side effects beyond launching the app.

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?

Concise, front-loaded with purpose, then explains output format. No unnecessary repetition. Could be slightly more structured with bullet points for the format.

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?

Given no output schema, description explains the return format well. Covers parameters implicitly. Lacks error handling or prerequisites, but adequate for a connector 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?

Schema has 100% description coverage for parameters, so description adds minimal extra value. It mentions verbose:true for diagnostics, which is helpful but not critical.

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?

Clearly states it connects to an Android emulator/device and launches an app, returning the initial UI screen. Differentiates from sibling tools (e.g., agentest_get_ui_tree, agentest_run_flow) by being the first-step connection tool.

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?

Implied usage as the first step before other agentest tools. No explicit when-not or alternatives, but the context suggests it's the starting point.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arjun-vegeta/agenTest'

If you have feedback or need assistance with the MCP directory API, please join our Discord server