Skip to main content
Glama

phone_wait_for

Waits until specified text appears on the Android screen, then returns the current element list; useful for page loads and incoming messages.

Instructions

Wait until some text appears on screen (page loads, messages arriving). Returns the element list.

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

Input Schema

NameRequiredDescriptionDefault
textYes
timeoutNoms, default 10000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the call blocks until the condition is met and that it returns the element list, but it never says what happens on timeout (error, empty result, or partial list), which is the single most important behavioral question for a wait tool.

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

Conciseness4/5

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

Two short sentences with the action front-loaded and no filler; the parenthetical examples add value. It is arguably under-specified rather than padded, but the phrasing 'some text' is loose for a matching predicate.

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?

There is no output schema, and the description does cover the return value at a high level ('element list'). However, for a blocking wait with a timeout parameter, the absence of timeout-failure semantics leaves a real gap an agent needs filled.

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 coverage is 50%: timeout is documented in-schema but 'text' is not. The description says 'some text appears', hinting at substring matching, but does not clarify match semantics (substring vs exact, case sensitivity) or whether timeout units/behavior match the schema's 'ms, default 10000'.

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 and resource: wait until text appears on screen, with concrete triggers (page loads, messages arriving). It does not distinguish itself from the obvious sibling phone_elements, which an agent must infer is the non-waiting alternative.

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?

The parenthetical examples imply when this is appropriate (waiting for page loads or incoming messages), but there is no explicit statement of when to prefer phone_elements instead, nor any exclusion or prerequisite. Usage is implied rather than directed.

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