Skip to main content
Glama

Wait

browser_wait

Pause browser automation for a specified number of seconds so page transitions or animations can complete before the next action.

Instructions

Wait a number of seconds (for page transitions or animations).

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
secondsYesSeconds to wait

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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. It correctly conveys that the tool is a timed sleep rather than an event-based wait, but it omits whether the wait blocks the session, whether there is a maximum allowed duration, and whether it interacts with page load state. These are clear gaps for an unannotated tool, making it minimum viable.

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?

A single front-loaded sentence with a useful parenthetical and zero wasted words. The purpose and parameter are immediately clear.

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 output schema and no annotations, the definition is mostly complete: it says what it does, what it takes, and why you might use it. The only missing element an agent might want is a note on blocking behavior or duration limits, which is minor at this complexity.

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 100%, and the sole parameter 'seconds' is already documented in the schema as 'Seconds to wait'. The description adds only a use-case parenthetical, not parameter-specific meaning, so the baseline 3 is appropriate.

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 (wait) and resource (number of seconds) and even hints at the use case (page transitions or animations). It is clearly distinguishable from all siblings, none of which pause execution, though it does not explicitly call that out.

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 a clear context for use — page transitions or animations — which tells an agent when to reach for it. There is no explicit when-not guidance (e.g., don't use as a substitute for waiting on a selector or network idle), but the intended scenario is well framed.

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