Skip to main content
Glama

wait_for

Read-only

Delay browser actions until specified text appears or disappears, or for a set time, enabling agents to sync with page changes.

Instructions

Wait until some text appears or disappears, or for a number of milliseconds.

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

Input Schema

NameRequiredDescriptionDefault
msNo
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.
goneNoWait for the text to disappear instead.
textNo
timeoutNoDefault 15000 ms.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a non-destructive read operation. The description adds that it can wait for text or a duration, but it does not explain timeout behavior, blocking semantics, or what happens when the condition is not met.

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?

The definition is a single compact sentence with no wasted wording, and the primary waiting conditions are front-loaded. It is appropriately sized for a simple wait tool.

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?

The tool is conceptually simple and has no output schema, but the description does not clarify default behavior when no parameters are provided or how timeout interacts with the wait condition. It is adequate but leaves some operational details implicit.

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 60%, with descriptions for tab, gone, and timeout, while text and ms are undocumented in the schema. The description introduces the core concepts of text appearance/disappearance and milliseconds, partially compensating for the gap but not explaining tab selection or timeout behavior.

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 states a specific verb and resource: wait for text appearance/disappearance or a fixed number of milliseconds. This is clear enough to distinguish the tool from siblings that wait for downloads or users, though it does not explicitly name those alternatives.

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 description implies when to use the tool by describing its waiting conditions, but it gives no explicit when-not guidance or comparison to alternatives like wait_for_download or wait_for_user. Usage is inferable but not fully guided.

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