Skip to main content
Glama

ios_swipe

Perform a swipe gesture between two screen coordinates on an iOS or iPadOS device, with optional duration in milliseconds, to automate touch interactions.

Instructions

Swipe from (x1, y1) to (x2, y2) with duration in milliseconds.

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

Input Schema

NameRequiredDescriptionDefault
x1Yes
x2Yes
y1Yes
y2Yes
duration_msNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden, yet it says nothing about whether the call blocks until the gesture finishes, what happens if coordinates fall outside the screen bounds, or whether it requires the target app to be foregrounded. It only restates the input geometry; the safety and side-effect profile is entirely undocumented.

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 sentence with zero filler, front-loading the gesture and the coordinate path. It is arguably too terse for a five-parameter gesture tool, but nothing in it is redundant.

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

Completeness2/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 not be described. However, for a coordinate-driven gesture tool with no annotations and five undocumented-parameter surfaces, the absence of coordinate units, preconditions, and device/simulator targeting leaves the definition materially incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does clarify that x1/y1 is the start and x2/y2 the end point and that duration is in milliseconds (adding units beyond the bare 'Duration Ms' title), but it never states the coordinate space (points vs pixels), the origin convention, or that duration defaults to 250ms.

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 specific verb (swipe) and the exact resource geometry (from (x1,y1) to (x2,y2)) plus duration, which distinguishes it from a tap gesture. It stops short of explicitly differentiating itself from siblings like ios_tap or any scroll helper, so an agent must infer the boundary from the name alone.

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 guidance on when to use a raw coordinate swipe versus element-based alternatives such as ios_tap_element, nor any precondition (app in foreground, element visible, screen size limits). The agent gets mechanics but no selection criteria.

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