Skip to main content
Glama

gesture-rotate

Rotate on-screen content by simulating a two-finger circular arc gesture. Use for rotating maps, images, or UI elements in iOS simulators and Android emulators.

Instructions

Send a two-finger circular arc gesture to rotate on-screen content by a specified angle. Two fingers are placed opposite each other at a fixed radius from the center, then swept from startAngle to endAngle degrees. All positions and radius are normalized 0.0–1.0 (fractions of screen width/height, not pixels)—same coordinate space as gesture-tap and gesture-swipe. endAngle > startAngle = clockwise rotation. Typical values: radius 0.15, startAngle 0, endAngle 90 for a 90° clockwise turn. Auto-generates interpolated frames at ~60fps. Unlike gesture-pinch which moves fingers linearly to zoom, this orbits fingers in an arc to change orientation. Use when you need to rotate a map, image picker, or any rotateable UI element. Returns { rotated: true, timestampMs }. Fails if the simulator-server / emulator backend is not reachable for the given device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
udidYesTarget device id from `list-devices` (iOS UDID or Android serial).
radiusYesDistance from center to each finger: normalized 0.0–1.0 (fraction of screen, not pixels). E.g. 0.15 = fingers placed 15% of screen away from center.
centerXYesCenter of rotation, horizontal: normalized 0.0–1.0 (fraction of screen width, not pixels)
centerYYesCenter of rotation, vertical: normalized 0.0–1.0 (fraction of screen height, not pixels)
endAngleYesEnding angle in degrees. endAngle > startAngle = clockwise.
durationMsNoTotal gesture duration in milliseconds (default 300)
startAngleYesStarting angle in degrees (0 = right, 90 = down)
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses gesture mechanics (two fingers at fixed radius, sweep), coordinate system, auto-generated frames at ~60fps, and return value. Missing details on potential side effects or cancellation, but adequate for a gesture tool.

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?

Description is three sentences, each serving a distinct purpose: action description, geometry & conventions, usage guidance. No redundancy or filler. Front-loaded with the core purpose.

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?

Covers gesture mechanics, typical values, direction, failure condition, and return type. Does not address parameter bounds or interruption behavior, but given sibling context and no output schema, it is largely complete for effective invocation.

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

Parameters4/5

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

Schema coverage is 100% (baseline 3). Description adds meaning beyond schema: explains clockwise direction (endAngle > startAngle), gives typical values (radius 0.15, start/end 0/90), and reinforces normalized coordinate interpretation.

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 clearly states the tool's action: 'Send a two-finger circular arc gesture to rotate on-screen content.' It specifies the verb (send), resource (gesture), and result (rotate). It also distinguishes from sibling 'gesture-pinch' by contrasting linear vs. arc motion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Provides explicit use-case guidance: 'Use when you need to rotate a map, image picker, or any rotateable UI element.' Also mentions failure condition. No explicit when-not, but does name an alternative (gesture-pinch). Lacks full exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/software-mansion/argent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server