Skip to main content
Glama

android_tap_element

Destructive

Taps a single enabled Android UI element by exact text, content description, or resource ID, and fails on ambiguous matches so you can inspect the screen and use coordinates instead.

Instructions

Tap one enabled element identified by exact text, content description or resource ID. Fails if ambiguous; inspect screen and use coordinates.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "match": "<match>",
      "field": "<field>"
    },
    "name": "android_tap_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYes
matchYes
deviceNoOptional connected device id, connection serial or exact model. Overrides the selected/default phone for this call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.3

TDQS

A3.6/5.0
Behavior3/5

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

Adds behavior beyond annotations: only enabled elements are tappable, and ambiguous matches produce a failure rather than a guess. It does not explain what the tap changes, that state mutation is irreversible (destructiveHint=true already flags this), or what a success response looks like.

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?

Two tightly packed sentences with the identification modes front-loaded and the failure/fallback guidance second. The closing clause ('inspect screen and use coordinates') is terse to the point of ambiguity about which tool performs that inspection.

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

Completeness3/5

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

For a three-parameter destructive mutation with no output schema, the description covers matching and failure mode but omits preconditions (app in foreground, element visible/enabled already stated), success return shape, and guidance on the undocumented device parameter.

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 coverage is 33%, with only the device parameter documented. The description compensates partially by mapping the three field enum values to plain meaning and stressing 'exact' matching, but it says nothing about the device override or match-string edge cases such as special characters.

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?

States a specific verb (tap) and resource (one enabled element) plus the three identification modes it accepts. It implicitly separates itself from android_tap by saying to fall back to coordinates, though it never names the sibling directly.

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?

Gives a clear selection condition (use when you can identify the element by exact text/description/resourceId) and an explicit fallback path ('inspect screen and use coordinates'). It lacks an explicit statement of when not to use it, e.g. for disabled or off-screen elements.

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