Skip to main content
Glama

app_tap

Press a button or pressable element in a live Expo app and return the resulting screen changes plus any new errors.

Instructions

Press a button/pressable element. Returns what changed on screen plus any new errors.

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

Input Schema

NameRequiredDescriptionDefault
refNoref from the last snapshot, e.g. "e4"
fullNofull screen instead of a diff
longNolong press
textNovisible label/placeholder (exact match first, then contains)
testIDNotestID prop of the element
snapshotNoreport the screen afterwards (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose one meaningful behavior: the return payload (screen changes plus new errors). It says nothing about failure modes — stale or missing ref, ambiguous selector matches, or whether the tap is a no-op when nothing matches — which leaves real gaps for a UI-mutating 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?

Two short sentences, front-loaded with the action and followed by the return contract. Nothing is redundant or padded.

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 description covers the return value, which matters since there is no output schema, and the schema covers all six optional parameters. However, with zero required parameters and multiple interchangeable selectors (ref, text, testID), the description never explains which selector wins or how to recover from a failed press — a material gap for this tool's complexity.

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, and the description adds no parameter-level meaning beyond it. Baseline 3 applies; notably it does not explain selector precedence among the six optional parameters.

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?

"Press a button/pressable element" gives a specific verb and resource, and the framing (pressable element) separates it from siblings like app_type, app_scroll, and app_toggle. It stops short of explicitly naming which sibling to use for adjacent interactions, so it is clear but not maximally differentiated.

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?

The description contains no when-to-use or when-not-to-use guidance, no prerequisite stating that a ref must come from a prior snapshot, and no mention of when app_type or app_toggle is the better choice. Usage context is at best implied by the word "press".

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