Skip to main content
Glama
Sign In
ios-control-mcp

ios-control-mcp

by als0m3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

iphone_swipe

Performs a swipe between normalized coordinates on a connected iPhone with a configurable duration to automate touch gestures; avoid starting at the bottom edge to prevent iOS system gestures.

Instructions

Drag from (x,y) to (x1,y1), normalised 0.0–1.0. Avoid starting at the very bottom edge: iOS reads that as a system gesture and leaves the app.

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": {
      "x": "<x>",
      "y": "<y>",
      "x1": "<x1>",
      "y1": "<y1>"
    },
    "name": "iphone_swipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
msNoGesture duration (default 300).
x1Yes
y1Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden, and it delivers a non-obvious behavioral hazard: a swipe starting at the bottom edge triggers a system gesture and exits the app. That is exactly the kind of context an agent cannot get from the schema. It omits return behavior and whether the call blocks, which keeps it short of a 5.

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 sentences, nothing wasted. The primary mechanics are front-loaded and the caveat follows as a secondary constraint, which is the right order for a gesture tool.

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?

For a five-parameter gesture tool with no annotations and no output schema, the description covers the call mechanics, the coordinate system, and the main failure mode. What is missing is any statement about the response or side effects, which is minor for a device-input action.

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 only 20% (just ms), so the description must compensate, and it does: it explains that x, y, x1, y1 are normalised 0.0–1.0 and which pair is the start versus the end. Only ms remains undocumented in prose, but the schema covers it.

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 concrete verb and resource ('Drag from (x,y) to (x1,y1)') and defines the coordinate frame in the same sentence, so an agent knows exactly what action it performs. It is distinguishable from iphone_tap by the start/end point pair, though it never names that sibling explicitly.

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

Usage Guidelines3/5

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

Gives one genuinely operational constraint ('avoid starting at the very bottom edge' because iOS intercepts it), which is a when-not-to rule. It does not, however, say when to prefer a swipe over iphone_tap or iphone_button, so alternative selection is left to inference.

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