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

ios-control-mcp

by als0m3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

iphone_tap

Tap an iPhone screen at normalized coordinates (0.0–1.0), with optional hold duration, to automate UI interactions through ios-control-mcp.

Instructions

Tap the screen once. Coordinates are NORMALISED from 0.0 to 1.0 (x=0 is the left edge, y=0 the top), never pixels.

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>"
    },
    "name": "iphone_tap"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
hold_msNoContact duration (default 120).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that coordinates are normalized rather than pixels, but it does not state prerequisites such as device connection or foreground app state, nor what side effects or response the agent should expect.

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?

The description is two concise sentences with the core action front-loaded and the critical coordinate convention following immediately. There is no redundant or wasted wording.

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?

For a simple tap action, the description covers the main parameter pitfall: normalized coordinates. However, with no annotations and no output schema, it remains silent on device targeting, prerequisites, and result behavior, which leaves some context for an agent to infer.

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 33%, and the schema gives no descriptions for x and y besides numeric bounds. The description compensates well by explaining the normalized 0.0–1.0 coordinate system and the origin direction, though it does not add meaning for the optional hold_ms parameter beyond its 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 gives a specific verb and resource: 'Tap the screen once.' This clearly distinguishes the tool from siblings such as iphone_swipe, iphone_type, and iphone_button without requiring the schema to be opened.

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?

The description provides no explicit when-to-use guidance, no exclusions, and does not name alternatives such as iphone_swipe for gestures or iphone_button for hardware controls. The intended usage is only implied by the tool name and description.

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