Skip to main content
Glama

app_wait

Blocks until specified text or testID appears or disappears, eliminating repeated snapshot polling when synchronizing with a live Expo app.

Instructions

Wait until text or a testID appears (or disappears with gone=true). Cheaper than polling snapshots.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "app_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
goneNo
textNo
testIDNo
timeoutNoms, default 5000, max 30000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full load. It discloses the blocking/wait semantics and the gone=true inversion, which is genuine value, but it omits what happens on timeout (error versus a falsy return), whether the call blocks the agent for up to 30s, and what it returns on success.

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 short sentences, condition first and the comparative cost note second. Nothing is padded and the most decision-relevant fact (what it waits for) leads.

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 four-parameter tool with no annotations and no output schema, the definition covers the happy path adequately but leaves the agent guessing about return values, timeout behaviour, and the relationship between text and testID. Those gaps matter for correctly composing a wait step in a test flow.

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 only 25% (only timeout is documented in schema), so the description has to compensate. It does explain gone=true, but leaves unclear whether text and testID are combined as AND or OR, whether either is required, and it never mentions the timeout parameter's failure mode.

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?

The description gives a specific verb plus the condition it waits on ('Wait until text or a testID appears') and names the disappearance case, which is far more informative than the bare name app_wait. It implicitly contrasts with snapshot-based polling but never names app_snapshot, so the differentiation is implied rather than explicit.

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 states the core use case (block until a condition holds) and offers a clear cost-based rationale for choosing it over reposurveying state with snapshots. There is no explicit 'do not use when' guidance, e.g. for cases where you need the full tree rather than a single element.

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