Skip to main content
Glama

iphone_press_button

Press an iPhone hardware button to return to the home screen or adjust the volume by one step.

Instructions

Press a hardware button of the iPhone.

iPhones have no back button: to go back inside an app, tap its back button (often top left, see
iphone_ui_tree). To leave an app use 'home'; to quit it completely use iphone_close_app; to lock the
screen use iphone_lock.

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

Input Schema

NameRequiredDescriptionDefault
buttonYes'home' returns to the home screen (leaves the current app running in the background); 'volumeUp' / 'volumeDown' change the volume by one step.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / button / description
      Added value: +"'home' returns to the home screen (leaves the current app running in the background); 'volumeUp' / 'volumeDown' change the volume by one step."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds the key behavioral consequence that 'home' only backgrounds the app rather than terminating it, and steers to iphone_close_app for termination — meaningful state context beyond the annotations. It does not discuss any rate/latency or repeated-press effects, which keeps it below a 5.

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?

Front-loaded with the one-line purpose, then a compact routing paragraph where every clause maps to a distinct sibling. Slightly redundant because the 'home leaves the app running' point also appears in the schema's parameter description, but the sentence is short and the redundancy is low-cost.

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?

With one enum-constrained parameter, full schema coverage, an output schema present, and rich annotations, the description covers everything needed to select and invoke it. Return values need not be described since an output schema exists; only minor behavioral detail (e.g. what a volume press at max volume does) is absent.

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?

The single 'button' enum is fully documented in the schema (100% coverage) including the semantics of 'home' versus 'volumeUp'/'volumeDown'. The description restates the 'home' behavior but adds no syntax, ordering, or edge-case information the schema lacks, so the baseline 3 applies.

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 and resource ('Press a hardware button of the iPhone'), then immediately disambiguates from the nearest alternatives by name: back-navigation is iphone_tap on the app's back button, leaving an app is 'home', quitting is iphone_close_app, locking is iphone_lock. An agent can pick the right tool 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 Guidelines5/5

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

Explicit routing rules are given for each alternative action, plus a proactive correction of a likely wrong assumption ('iPhones have no back button' → use iphone_ui_tree / tap instead). This is exactly the when-to-use and when-not-to-use guidance an agent needs to avoid calling this for navigation.

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