Skip to main content
Glama
Sign In
open-browser-control

open-browser-control

by smankoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_wait

Wait for an element to appear, specific text to show, or a set duration before proceeding. Ensure conditions are met with a configurable timeout.

Instructions

Wait for a condition: element to appear, text to show, or fixed time.

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

Input Schema

NameRequiredDescriptionDefault
msNoWait fixed milliseconds
textNoWait for text to appear on page
timeoutNoMax wait time in ms (default: 10000)
selectorNoWait for element matching selector

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided; description only lists condition types without detailing behavior like combination logic, error handling, or return value. Schema adds timeout default but description adds minimal behavioral context.

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?

Single 11-word sentence, front-loaded with key action and conditions, efficiently conveying purpose without waste.

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 wait tool with 4 params and no output schema, the description lacks context on combining conditions, error behavior, or practical usage scenarios. Schema partially compensates but overall incomplete.

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 has 100% description coverage; the description paraphrases schema fields (ms, selector, text) without adding new semantic meaning. Baseline 3 applies.

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?

The description clearly states the action (wait) and the conditions (element, text, fixed time), distinguishing it from sibling tools like browser_click or browser_navigate.

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 usage for waiting on page conditions but provides no explicit when-to-use or alternative guidance. No exclusion criteria mentioned.

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