Skip to main content
Glama

ios_tap

Simulates a tap at specific screen coordinates (x, y) on an iOS or iPadOS device, letting MCP clients trigger UI interactions at exact points without manual touch input.

Instructions

Tap at screen point coordinates (x, y).

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": "ios_tap"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and largely fails it. It does not disclose the coordinate origin (top-left vs. center), units (points vs. pixels on Retina devices), whether the tap is instantaneous or long-press capable, or what device state is required for success.

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

Conciseness3/5

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

A single clean sentence with zero padding and the key concept front-loaded as the verb. However, its brevity stems from under-specification rather than tight editing, so it earns only a middling score.

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 tool is intrinsically simple (two required integers) and an output schema exists, so return values need not be explained. Still, the absence of annotations plus the unspecified coordinate system leaves a meaningful gap an agent would hit on first invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% — both parameters are bare integers titled 'X' and 'Y'. The description adds only 'screen point coordinates', which hints at the domain but omits origin, valid range, and units, so an agent cannot reliably construct correct values.

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 specific verb ('Tap') and a specific resource ('screen point coordinates'), so an agent knows this performs a synthetic touch at an absolute position. It does not explicitly contrast with the sibling ios_tap_element, but the coordinate-based framing makes the distinction inferable.

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?

There is no guidance on when to prefer this coordinate tap over ios_tap_element, nor any prerequisite state (app launched, screen on, UI settled). The agent must infer usage entirely from the name.

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