Skip to main content
Glama

iphone_wait_for

Read-onlyIdempotent

Waits for specified text to appear on an iPhone screen or disappear with gone=true after loading, navigation, or animation. Polls until the condition holds, avoiding guessed delays.

Instructions

Wait until an element with the given text appears on screen (or disappears with gone=true).

Use it after an action that triggers loading, navigation or an animation, instead of guessing a delay or taking repeated screenshots. Polls about twice a second and returns as soon as the condition holds, with the element's position, or reports a timeout. Reads only.

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": {
      "text": "<text>"
    },
    "name": "iphone_wait_for"
  }
}

Input Schema

NameRequiredDescriptionDefault
goneNofalse waits until the text appears; true waits until it disappears (e.g. a spinner or 'Loading').
textYesText to wait for, matched case-insensitively against element labels, names and values.
exactNotrue requires the whole label to equal the text instead of containing it.
timeoutNoMaximum seconds to wait (1–60).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, destructive=false), the description discloses the polling cadence ('about twice a second'), that it returns as soon as the condition holds, that it returns the element's position, and that it reports a timeout. It does not clarify whether a timeout is an error or a normal return value, which is the one behavioral gap left.

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 purpose and the key mode switch are front-loaded in the first sentence, and the second sentence covers usage and runtime behavior without repetition. Every clause carries information and nothing is wasted.

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 polling wait tool with annotations and an output schema, the description covers purpose, usage, timing, and return content adequately. The only missing piece is timeout semantics (error versus result), which is a minor gap given the output schema likely covers the shape.

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 text, gone, exact, and timeout in detail. The description only references 'gone=true' in passing and adds no matching semantics, format details, or defaults beyond what the schema provides; baseline 3 applies.

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 states a precise verb and resource ('Wait until an element with the given text appears on screen') and immediately covers the inverse mode ('disappears with gone=true'). It is clearly distinguishable from siblings like iphone_screenshot or iphone_tap_text without opening any schema.

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?

It gives a clear when-to-use rule: after an action that triggers loading, navigation, or an animation, and explicitly rules out 'guessing a delay or taking repeated screenshots.' The guidance is strong but stops short of naming specific sibling tools or stating when-not-to-use conditions.

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