Skip to main content
Glama

tap

Activates a UI element by ref or raw x,y coordinates in a live device session, letting coding agents drive and verify app interfaces.

Instructions

Tap an element by ref (e.g. @e5), or raw coordinates (e.g. 100,200).

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": {
      "target": "<target>"
    },
    "name": "tap"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesElement ref (e.g. @e5 or e5) or "x,y" coordinates.
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations supply only readOnlyHint=false, so the description carries nearly the full behavioral burden. It does not say what a tap triggers (navigation, toggles), whether it waits for the UI to settle, or what happens when the ref is stale or the coordinates hit nothing. Only the input formats are disclosed.

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 with zero filler; the verb and both accepted input forms appear immediately.

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 two-parameter, schema-rich tool this is close to sufficient on inputs, but with no output schema and only a minimal annotation, the agent still lacks any picture of post-tap behavior or failure modes.

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% and the schema already explains both target and the session_id fallback chain, so the baseline is 3. The description's examples of the two accepted target syntaxes mildly reinforce the schema but add no meaning beyond it.

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 the two accepted targeting modes with concrete examples (@e5, 100,200). It does not differentiate itself from close siblings like press, long_press, or tap_focused, so the agent must infer that plain 'tap' is the short single-touch gesture.

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

Usage Guidelines2/5

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

No statement of when to choose this over press, long_press, or tap_focused, and no prerequisites or preconditions (e.g. needing a ref from find or a screenshot). Usage is only implied by the verb.

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