Skip to main content
Glama

gesture

Execute structured touch gestures such as pan, swipe, pinch, and rotate on real devices to simulate user interactions for testing and debugging.

Instructions

Run a structured gesture.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory for command execution.
kindYesGesture variant.
udidNoiOS device UDID selector.
debugNoEnable debug diagnostics.
deltaNoMovement delta for pan or transform gestures.
runIdNoLease run identifier.
scaleNoPinch or transform scale.
deviceNoDevice name selector.
originNoGesture origin point.
presetNoSwipe preset.
serialNoAndroid serial selector.
targetNoAlias for deviceTarget on commands without a UI target field. Interaction commands reserve target for the UI element.
tenantNoRemote tenant identifier.
degreesNoRotation in degrees.
leaseIdNoExisting lease identifier.
sessionNoAgent-device session name.
distanceNoFling distance.
platformNoPlatform selector used to resolve a device.
stateDirNoAgent-device state directory.
velocityNoRotate gesture velocity.
directionNoFling direction.
durationMsNoGesture duration in milliseconds.
deviceTargetNoDevice target form. Maps to the CLI --target flag.
daemonBaseUrlNoRemote daemon base URL.
daemonAuthTokenNoRemote daemon auth token.
iosXctestEnvDirNoWritable directory for iOS XCTest runner env overlays.
mcpOutputFormatNoMCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.
iosXctestrunFileNoExternally built iOS XCTest runner .xctestrun artifact path.
iosSimulatorDeviceSetNoiOS simulator device-set path used for device resolution.
androidDeviceAllowlistNoAndroid serial allowlist used for device resolution.
iosXctestDerivedDataPathNoDerived data path for external iOS XCTest runner execution.
Behavior1/5

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

No annotations are provided, and the description gives no behavioral information. The tool has 31 parameters, but the description does not disclose any side effects, permissions, or output behavior, leaving the agent blind to important traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

While very concise at one sentence, it is under-specified. The description could be expanded to include key context, making it more useful without sacrificing conciseness.

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

Completeness1/5

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

Given 31 parameters, no output schema, no annotations, and a minimal description, the tool definition is severely incomplete. It fails to explain the gesture concept, expected outcomes, or parameter relationships.

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 description coverage is 100%, so the schema already documents all parameters. The description adds no additional meaning beyond what's in the schema, meeting the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Run a structured gesture' uses a verb and a resource, but it's vague. It doesn't specify what a gesture entails or distinguish from sibling tools like swipe or scroll, which are also gestures.

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?

No guidance on when to use this tool versus alternatives like click, longpress, or scroll. The description implies it's for any structured gesture, but without context, the agent may misuse it.

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/callstack/agent-device'

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