Skip to main content
Glama

gesture-rotate

Rotate on-screen content by a specified angle using a two-finger circular arc gesture. Use for maps, image pickers, or any rotatable UI element.

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 radii 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. A single radius applies to both axes, so on a non-square screen it traces a physical ellipse (finger separation varies through the turn); pass radiusX+radiusY (fractions of width/height with radiusX·width = radiusY·height) for a physically circular orbit instead. 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).
radiusNoDistance 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. One value for both axes, so on a non-square screen the orbit is a physical ellipse — pass radiusX+radiusY instead for a true circle. Required unless radiusX and radiusY are given.
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)
radiusXNoPer-axis finger distance, horizontal: normalized 0.0–1.0 fraction of screen WIDTH. Give both radiusX and radiusY (they override radius) with radiusX·screenWidth = radiusY·screenHeight for a physically circular orbit — constant finger separation, no pinch coupled into the turn.
radiusYNoPer-axis finger distance, vertical: normalized 0.0–1.0 fraction of screen HEIGHT. Always paired with radiusX — see radiusX.
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?

With no annotations, the description fully carries the burden of behavioral disclosure. It explains the mechanics (two fingers, radius, angles), normalized coordinates, ellipse vs. circle for non-square screens, auto-generated ~60fps frames, return value, and failure condition. It could mention prerequisites like device boot status, but the failure condition partially covers that.

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?

The description is well-structured, starting with purpose then details. It is somewhat long but every sentence adds value, including usage guidelines and behavioral details. It could be slightly more concise, but it's not wasteful.

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?

Given the complexity of a multi-parameter gesture tool with no output schema, the description is remarkably complete: it covers coordinate space, angle semantics, radius handling, elliptical distortion, comparison to sibling, typical usage, return value, and failure mode. No gaps are evident.

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 description coverage is 100%, so baseline is 3. The description adds extra meaning: explains coordinate system (normalized 0-1), rotation direction (endAngle > startAngle = clockwise), typical values (radius 0.15, startAngle 0, endAngle 90), and the trade-off between radius and radiusX+radiusY for non-square screens.

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 starts with a clear, specific verb+resource: 'Send a two-finger circular arc gesture to rotate on-screen content by a specified angle.' It explicitly distinguishes the tool from gesture-pinch, which is present in sibling tools, by noting that pinch moves fingers linearly while rotate orbits fingers.

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?

The description explicitly states when to use this tool: 'Use when you need to rotate a map, image picker, or any rotateable UI element.' It also contrasts with gesture-pinch, providing clear alternative guidance.

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