Skip to main content
Glama

iphone_swipe

Drag one finger between start and end coordinates to perform precise iOS gestures, including moving sliders, reordering items, revealing row actions, or pulling down notifications.

Instructions

Drag one finger from a start point to an end point.

Use it for precise drags: sliders, reordering, swiping a cell to reveal actions, pulling down the
notification area or a sheet. For plain scrolling of a list or page, iphone_scroll is simpler.
Swipes starting at the very bottom or top edge trigger iOS system gestures (home, notifications).

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": {
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>"
    },
    "name": "iphone_swipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1YesStart x in iOS points.
x2YesEnd x in iOS points.
y1YesStart y in iOS points.
y2YesEnd y in iOS points.
duration_msNoDuration of the movement in milliseconds (50–5000); short is a flick, long is a drag.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.2.0
    • addedInput schema / properties / duration_ms / description
      Added value: +"Duration of the movement in milliseconds (50–5000); short is a flick, long is a drag."
    • addedInput schema / properties / duration_ms / maximum
      Added value: +5000
    • addedInput schema / properties / duration_ms / minimum
      Added value: +50
    • addedInput schema / properties / x1 / description
      Added value: +"Start x in iOS points."
    • addedInput schema / properties / x1 / minimum
      Added value: +0
    • addedInput schema / properties / x2 / description
      Added value: +"End x in iOS points."
    • addedInput schema / properties / x2 / minimum
      Added value: +0
    • addedInput schema / properties / y1 / description
      Added value: +"Start y in iOS points."
    • addedInput schema / properties / y1 / minimum
      Added value: +0
    • addedInput schema / properties / y2 / description
      Added value: +"End y in iOS points."
    • addedInput schema / properties / y2 / minimum
      Added value: +0
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, non-idempotent, non-destructive), the description adds genuinely useful behavioral context: swipes from the very bottom or top edge trigger iOS system gestures like home or notifications. It does not cover what happens if coordinates land off-screen or how the gesture is confirmed, so it stops short of full transparency.

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?

Three short sentences, front-loaded with the core action, then use cases, then the sibling alternative, then the edge-gesture caveat. No filler and no repetition of schema fields.

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?

An output schema exists, so return values need no explanation, and the description covers purpose, alternatives, and the main failure mode (edge system gestures). What's missing is minor: coordinate origin/units guidance beyond the schema's "iOS points" and any note on what happens with out-of-bounds coordinates.

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 x1/y1/x2/y2 documented in iOS points and duration_ms documented with its 50–5000 ms range and flick-vs-drag meaning. The description adds no coordinate-space or duration detail beyond the schema, 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?

"Drag one finger from a start point to an end point" gives a concrete verb (drag) and resource (finger gesture) with clear start/end geometry. It explicitly distinguishes itself from the sibling iphone_scroll, so an agent can route between the two without opening a 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?

Names concrete use cases (sliders, reordering, swipe-to-reveal, pulling down notification area or a sheet) and names the alternative with the condition that selects it: plain list/page scrolling goes to iphone_scroll. It also flags the exclusion case where a swipe would trigger system gestures.

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