Skip to main content
Glama
Sign In
run-sequence-android-mcp

run-sequence-android-mcp

by nasiosheva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Screen Elements

android_list_elements
Read-only

List current screen UI elements with text, accessibility labels, resource ids, and pixel coordinates to find where to tap. Do not cache the result.

Instructions

List UI elements on the current screen with text, accessibility labels, resource ids, and pixel coordinates. Use this to find where to tap. Do not cache this result.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice id (serial or host:port). Optional -- when omitted, uses ANDROID_MCP_DEVICE env or auto-selects the connected device (physical devices preferred over emulators).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds behavioral details: it returns coordinates and UI attributes, and warns against caching. This complements the annotations well, though it could mention that the list is of visible elements only.

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, no filler. The first sentence conveys the core capability, and the second adds usage guidance and a critical warning. Every word earns its place.

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

Completeness5/5

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

For a simple list tool with one optional parameter and no output schema, the description fully covers what the tool returns and how to use it. The warning about caching adds important context.

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?

Since schema description coverage is 100% (the only parameter 'device' is fully described in the schema), the baseline is 3. The tool description adds no further parameter meaning beyond what the schema provides.

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 lists UI elements on the current screen with specific attributes like text, accessibility labels, resource ids, and pixel coordinates. This verb+resource combination distinguishes it from sibling tools that perform actions (tap, type, etc.) or query device info.

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 says 'Use this to find where to tap,' providing clear usage context. It also warns 'Do not cache this result,' which is important for dynamic screens. While it doesn't explicitly exclude scenarios, the guidance is direct and practical.

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