Skip to main content
Glama

wait

Pauses briefly for the Android UI to settle, up to 10000 ms, so subsequent screen reads or taps run against a stable interface.

Instructions

Wait for the UI to settle, up to 10000 ms. To wait for something to happen, wait_for is quicker and surer.

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": {
      "ms": "<ms>"
    },
    "name": "wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
msYesMilliseconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.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, and it does add one genuinely useful fact not in the schema: the 10000 ms ceiling. However, it doesn't say what happens if a larger value is passed (clamp, error, or ignore), whether the call blocks the agent, or what it returns. Minimum viable disclosure for a sleep-style primitive, but not rich.

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, no filler, and the primary behavior is front-loaded before the alternative is mentioned. Every clause carries information an agent needs.

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 one-parameter tool with no annotations and no output schema, the description covers purpose, the upper time bound, and the sibling trade-off, which is close to sufficient. The remaining gap is failure/clamping behavior for out-of-range ms values, a minor omission for a timing primitive.

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

Parameters4/5

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

Schema coverage is 100% ("ms: Milliseconds"), so the schema already defines the single parameter, and the baseline would be 3. The description earns one extra point because it supplies an upper bound of 10000 ms that appears nowhere in the schema, adding real constraint semantics rather than restating the field.

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?

"Wait for the UI to settle, up to 10000 ms" states a specific action, its target (UI settling), and a hard bound, which is far more precise than the bare name "wait". It also explicitly positions itself against the sibling wait_for, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

The second sentence names the alternative tool (wait_for) and the condition that selects it ("to wait for something to happen"), which implicitly defines this tool's own domain as passive UI settling. Both the when and the when-not are covered in a single clause.

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