Skip to main content
Glama

tap

Selects an element by read_screen ID or screen pixel coordinates, returning NOTHING CHANGED when the screen is unchanged and not clicking elements under other windows.

Instructions

Tap an element (by id from the last read_screen) or a screen coordinate in pixels. The result says NOTHING CHANGED when the screen reads the same afterwards, and an element under another window isn't tapped.

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

Input Schema

NameRequiredDescriptionDefault
xNoX in screen pixels
yNoY in screen pixels
elementNoElement id from read_screen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the NOTHING CHANGED outcome semantics and the occlusion rule (an element under another window won't be tapped). It omits other traits a mutating tool could use, such as whether the tap blocks until the UI settles or how failures are reported.

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, front-loaded with the action and its two targeting modes, then the caveats. Nothing is padded or restated.

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?

Required parameters is 0, so an agent cannot tell from the description alone which arguments are needed to make a valid call, and the either/or relationship between element and x/y is unstated. For a 3-param mutation tool with no annotations and no output schema, that is a real gap despite the useful behavioral notes.

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 100%, so each of x, y, and element is already documented. The description adds only that the id comes from the last read_screen and that coordinates are screen pixels — no explicit statement that element and x/y are mutually exclusive alternatives, which is the one semantic gap left.

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?

States a specific verb (tap) and the two supported targets (element id from read_screen, or pixel coordinate), which is enough to separate it from siblings like long_press, swipe, and scroll without opening any schema.

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 clear context by tying the `element` argument to a preceding read_screen call and by warning that tapping is bound to coordinates/screen state. It does not state when to prefer coordinates over element ids, or when to use long_press instead, so it stops short of explicit alternatives.

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