Skip to main content
Glama

android_tap_element

Taps an Android UI element by coordinates or by text, resource_id, or content_desc, and records the transition edge into the Spatial Graph for deterministic navigation.

Instructions

Taps an Android UI element by coordinates (x, y) or semantic text / resource_id / content_desc, recording the transition edge into the Spatial Graph.

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

Input Schema

NameRequiredDescriptionDefault
xNoExact screen X coordinate.
yNoExact screen Y coordinate.
textNoCase-insensitive substring match against node text.
resource_idNoMatch against view resource-id.
content_descNoSubstring match against content-desc.
device_serialNoOptional ADB device serial. Defaults to the first connected device.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations present, the description carries the full behavioral burden, and it does disclose one genuinely non-obvious trait: the tap records a transition edge into the Spatial Graph. However, it says nothing about how ambiguous matches are resolved, wait/settle behavior, or what happens on failure, leaving meaningful gaps for a mutation tool.

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?

A single front-loaded sentence naming the action, the two addressing paths, and the side effect, with no filler or repetition.

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?

The tool has six all-optional parameters and no required field, yet the description never states that at least one selector or an x/y pair is needed, nor which selector wins on conflict. That omission is significant for correct invocation, though the Spatial Graph side effect is a useful addition.

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 every parameter is already documented in the schema. The description only restates the selector categories and adds no precedence, mutual-exclusivity, or coordinate-pairing rules 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?

The description gives a specific verb ('Taps') plus resource ('Android UI element') and names both addressing modes (coordinates or semantic selectors), while also disclosing the side effect of recording a Spatial Graph transition edge. This clearly separates it from siblings such as android_explore_and_click and android_navigate_to_node.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the two addressing modes, but the description never says when to prefer coordinates over text/resource_id/content_desc, nor how it relates to siblings like android_explore_and_click. No explicit when-not guidance or exclusions are provided.

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