Skip to main content
Glama

android_tap

Destructive

Taps a specified screen coordinate on an authorized Android phone to trigger UI actions; inspect the screen first to target the correct location.

Instructions

Tap a screen coordinate. Inspect the screen first.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "android_tap"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
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

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the agent knows this causes irreversible real-world change. The description's only added behavioral content is the 'inspect the screen first' caution, which is genuinely useful for a blind-tap tool but says nothing about out-of-bounds coordinates, failed taps, or what tapping outside an app's bounds does.

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 short sentences with zero filler, and the action is front-loaded before the caution. The extreme terseness borders on under-specification, but nothing in the text is wasted.

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

Completeness2/5

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

For a destructive, non-idempotent tool with three parameters, one-third schema coverage and no output schema, the two-sentence description leaves coordinate semantics and result/failure behavior unexplained. The annotations carry the safety profile, but the description does not do enough to make the call unambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — only 'device' is documented in the schema. The description adds no meaning to x/y beyond the schema's 0-20000 bounds, leaving the coordinate space (physical pixels vs dp, origin corner, rotation handling) entirely undefined, which is the critical semantic for a coordinate tap. This is a real gap the description should have closed.

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 and resource combination ('Tap a screen coordinate'), which is meaningfully more precise than a bare name restatement. It does not, however, distinguish itself from the sibling android_tap_element, leaving the agent to infer the coordinate-vs-element split from the names alone.

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?

'Inspect the screen first' implies a prerequisite workflow (look before tapping) but never states when to choose this over android_tap_element or android_swipe. Usage is implied rather than prescribed, with no exclusions.

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