Skip to main content
Glama

Wait

browser_wait
Read-only

Waits 0.5–10 seconds when a page is still loading or working, optionally returning once specified text appears or disappears, then reports what changed.

Instructions

Wait 0.5-10 seconds (until/gone: up to that, returning once the text appears or goes), then return what changed. Only for a page still loading or saying it is working: actions already wait for the requests they start.

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": {
      "seconds": "<seconds>"
    },
    "name": "browser_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
goneNoReturn once this text is gone
untilNoReturn once the page shows this text
secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior: with until/gone the wait returns as soon as the text appears or disappears, and seconds acts as an upper bound. It does not state what happens on timeout or what 'what changed' actually contains, which is the main behavioral gap.

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?

Two sentences, no filler, with the core duration and mode semantics front-loaded before the usage restriction. The nested parenthetical makes it slightly dense to parse but nothing is redundant.

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?

There is no output schema, so the description is the only source for return semantics, and 'return what changed' is too vague to tell an agent what it will receive. Timeout behavior and page-state failure modes are also unaddressed. For a simple read-only wait this is close to adequate, but the return-value vagueness is a real gap.

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 67% and the seconds property has no description in the schema, so the prose carries weight. The description explains that seconds is a cap when until/gone is supplied ('up to that, returning once the text appears or goes'), clarifying the interaction between the three parameters beyond their raw types and bounds.

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 names a specific action (wait 0.5-10 seconds) plus the conditional modes (until/gone) and states that it returns what changed. It is clearly a pause/poll tool rather than an interaction tool, though it never names a sibling explicitly.

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 gives an explicit constraint: 'Only for a page still loading or saying it is working: actions already wait for the requests they start.' That is a real when-not rule with reasoning, which discourages gratuitous use before clicks or typing. It stops short of naming a concrete alternative tool for any edge case.

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