Skip to main content
Glama
Sign In
ios-agent-driver

ios-agent-driver

by CodeJonesW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

swipe

Swipe or scroll between points on an iOS Simulator screen. Specify a direction from center or provide custom start and end coordinates.

Instructions

Swipe/scroll from one point to another. Either give a direction (auto-computed from screen center) or explicit from/to coordinates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "swipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
directionNo
from_xNo
from_yNo
to_xNo
to_yNo
duration_secNo
udidNoTarget simulator UDID. Defaults to the booted sim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It reveals that direction auto-computes from screen center, but does not mention duration behavior, return values, or whether the action blocks.

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?

Two concise sentences that front-load the core action and explain the two usage modes. No redundant words; every sentence earns its place.

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

Completeness3/5

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

The description covers the two main swipe modes but does not explain the duration_sec parameter or return behavior. Given no output schema and no annotations, some gaps remain for a complete understanding.

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 low (14%). The description adds meaning by explaining the relationship between direction and from/to coordinates, but omits details about duration_sec and udid (though udid has schema description).

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 performs a swipe/scroll gesture, distinguishing between direction-based (auto-computed from screen center) and explicit coordinate-based modes. This separates it from sibling tools like tap or press_button.

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?

The description specifies when to use direction vs explicit coordinates, providing clear context for usage. However, it does not explicitly compare to alternatives like tap for single-point gestures or press_button for long presses.

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

Deploy Server

Other Tools