Skip to main content
Glama

wait

Pause execution until a specified duration passes or a text, reference, or selector condition is met.

Instructions

Wait for duration, text, ref, or selector.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionNoAgent-device session name.
platformNoPlatform selector used to resolve a device.
deviceTargetNoDevice target form. Maps to the CLI --target flag.
targetNoAlias for deviceTarget on commands without a UI target field. Interaction commands reserve target for the UI element.
deviceNoDevice name selector.
udidNoiOS device UDID selector.
serialNoAndroid serial selector.
iosSimulatorDeviceSetNoiOS simulator device-set path used for device resolution.
androidDeviceAllowlistNoAndroid serial allowlist used for device resolution.
daemonBaseUrlNoRemote daemon base URL.
daemonAuthTokenNoRemote daemon auth token.
tenantNoRemote tenant identifier.
runIdNoLease run identifier.
leaseIdNoExisting lease identifier.
cwdNoWorking directory for command execution.
debugNoEnable debug diagnostics.
kindNo
durationMsNo
textNo
refNo
selectorNo
timeoutMsNo
depthNo
scopeNo
rawNo
stateDirNoAgent-device state directory.
Behavior2/5

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

No annotations are provided. The description simply states 'Wait for...' without disclosing whether the wait is blocking, how timeouts work, or any side effects. The agent is left to infer behavior from the schema parameters.

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

Conciseness2/5

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

The description is extremely short but lacks essential details. It is concise in word count but under-specified for a tool with 26 parameters. Better structure with explanations of each wait kind would improve usability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high parameter count (26) and no output schema, the single-sentence description is grossly inadequate. The agent cannot determine how to use parameters like timeoutMs, depth, scope, or how the wait kinds interact. The description fails to provide necessary context.

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 coverage is 65%, and the description names four wait kinds (duration, text, ref, selector) but does not explain how they map to the schema parameters like durationMs, text, ref, selector. The description adds minimal value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The tool name 'wait' and description 'Wait for duration, text, ref, or selector' convey the general purpose, but the description is vague and does not explain what each kind of wait entails. It distinguishes from sibling tools by being a waiting action, but lacks specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'find' or 'snapshot'. The description does not specify conditions for using different wait kinds or when to prefer other tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/callstack/agent-device'

If you have feedback or need assistance with the MCP directory API, please join our Discord server