Skip to main content
Glama

iphone_pinch

Performs a two-finger pinch gesture on an iPhone screen to zoom in or out in zoomable apps such as Maps, Photos, or web pages, with adjustable center point and scale.

Instructions

Two-finger pinch gesture to zoom in or out, e.g. in Maps, Photos or a web page.

Use it only where content is zoomable; elsewhere it usually has no effect. Single-finger gestures are
covered by iphone_tap, iphone_swipe and iphone_scroll.

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": {
      "scale": "<scale>"
    },
    "name": "iphone_pinch"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoCenter x in iOS points; default is the screen center.
yNoCenter y in iOS points; default is the screen center.
scaleYesZoom factor: above 1 zooms in (fingers apart, e.g. 2.0), below 1 zooms out (fingers together, e.g. 0.5). Range 0.2–5.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare openWorldHint, non-readOnly, non-idempotent and non-destructive, so safety is covered. The description adds genuine behavioral context beyond that: the gesture is a no-op on non-zoomable content, which sets correct expectations for failure. It stops short of saying what happens at scale limits or how the gesture interacts with app state, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, scope and effect front-loaded, then the exclusion and sibling routing. No filler, no repetition of schema content.

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

Completeness5/5

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

All three parameters are schema-documented, an output schema exists so return values need no prose, and the description covers purpose, applicability, failure mode and alternatives. Nothing an agent needs in order to call this correctly is missing.

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%, with x, y and scale all documented including defaults, range and direction semantics. The description adds nothing parameter-level beyond implying zoom direction, so 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?

The description states a specific gesture (two-finger pinch) and its effect (zoom in/out), plus concrete example surfaces (Maps, Photos, web page). It distinguishes itself from the single-finger siblings by naming them explicitly.

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 when-to-use ("only where content is zoomable") and an explicit consequence elsewhere ("usually has no effect"). It also routes the agent to iphone_tap, iphone_swipe and iphone_scroll for single-finger gestures, so the alternative selection is unambiguous.

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