Skip to main content
Glama
Sign In
phonedriver

phonedriver

by hridaya423
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

wait

Pauses until the device screen settles, specified text or @ref appears, or given text disappears, with an optional timeout.

Instructions

Wait for settled, a text (A|B for either) or @ref to appear, or gone:<text>.

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

Input Schema

NameRequiredDescriptionDefault
conditionYes
timeout_msNoDefault 5000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, yet it omits whether the call blocks, what it returns (boolean vs element vs error), and what happens when timeout_ms elapses. The only behavioral hint is the condition syntax; the 5000ms default lives in the schema, not the description.

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?

A single front-loaded sentence with no filler. Its terseness borders on under-specification, but every clause carries content relevant to invocation.

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

Completeness2/5

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

For a two-parameter tool with no annotations and no output schema, the definition should say what a successful wait yields and how timeout failure surfaces. Neither is covered, leaving an agent unable to predict return values or error handling.

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 50% and the undocumented parameter is `condition`, which the description meaningfully specifies: the `A|B` alternation, the `@ref` element form, and the `gone:` negation prefix all add semantics absent from the schema. It does not clarify how `gone:` combines with alternation or bare `settled`, but the core value space is conveyed.

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 ("Wait") and enumerates the condition forms it accepts (`settled`, literal text with `A|B` alternation, `@ref`, `gone:<text>`), which clearly separates it from action siblings like tap, swipe, or press. Clarity is slightly undercut because tokens like `settled` and `@ref` are never defined, so an agent must infer their meaning.

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?

Usage is only implied via the condition grammar: an agent can infer it waits for text to appear or disappear before acting. There is no explicit when-to-use versus alternatives, no guidance on choosing `settled` over a text condition, and no statement about what to do on timeout.

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

Deploy Server

Other Tools