Skip to main content
Glama

press

Send button and system gesture inputs—such as home, back, d-pad, or menu—to control live iOS, Android, Apple TV, Android TV, and Roku devices during UI verification.

Instructions

Press a device button or perform a system gesture (home, back, d-pad, etc).

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": {
      "button": "<button>"
    },
    "name": "press"
  }
}

Input Schema

NameRequiredDescriptionDefault
buttonYesButton to press. iPhone / iPad: home, back, lock, siri, enter, recents. Android phone / tablet: home, back, lock, enter, recents. Apple TV: dpad_up, dpad_down, dpad_left, dpad_right, dpad_center, back, home, menu. Android TV: dpad_up, dpad_down, dpad_left, dpad_right, dpad_center, back, home, enter. Roku: dpad_up, dpad_down, dpad_left, dpad_right, dpad_center, back, enter, up, down, left, right, select, backspace, play, rewind, forward, replay, info.
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 most of the burden and adds little: no statement about effect on app state, error behavior for unsupported buttons on a given platform (which the schema hints is a real risk), or latency/waiting semantics. Only the phrase 'system gesture' adds any behavioral color.

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?

A single front-loaded sentence with the action and resource stated first, no filler. The trailing 'etc' is mildly vague but does not undermine the structure.

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

Completeness4/5

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

For a two-parameter input tool with full schema coverage and no output schema, the description plus annotations cover what an agent needs to invoke it. A sentence on platform-dependent button validity or on how press differs from long_press would close the remaining gap.

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% and the button enumeration per platform plus the session_id fallback chain are fully documented in the schema, so the baseline of 3 applies. The description contributes no additional meaning or format detail beyond what the schema already states.

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 concrete verb ('Press') plus the resource ('a device button or perform a system gesture') and gives examples (home, back, d-pad). It is clearly distinct from pointer-based siblings like tap/swipe in kind, though it never names long_press, which is the closest ambiguous neighbor.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The reader must infer from 'home, back, d-pad' that this is for hardware/system-level buttons rather than on-screen coordinates; nothing directs them between press and long_press or tap.

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