Skip to main content
Glama
Sign In
chrome-fast

chrome-fast

by ventos312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

wait

Read-only

Pause Chrome automation until a CSS selector matches, text appears, network activity stops, or a fixed time passes, then return updated page content.

Instructions

Wait for a condition, then return the updated page content: an element matching a CSS selector, a piece of text appearing on the page, the network going quiet, or a 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": "wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoText; resolves once it appears in the page's visible text
timeNoFixed wait in ms (use instead of a condition)
timeoutNoMaximum wait for selector/text/networkIdle in ms (default: 5000)
selectorNoCSS selector; resolves once a matching element exists
networkIdleNoResolve once there has been no network activity for 500 ms

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered, and the description adds that the call returns refreshed page content. However, it omits key behavior: whether exactly one condition may be set, and what occurs on timeout (error vs. return current state).

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. The enumerated condition list mildly duplicates the schema, but it reads quickly and sets expectations correctly.

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

Completeness5/5

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

Contextual completeness score is 5.

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 description coverage is 100%, so the schema already documents each parameter including the 5000 ms default for timeout. The description restates the four conditions at a high level without adding syntax or precedence rules beyond the schema.

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") plus the four condition types and the return value (updated page content). An agent can distinguish it from siblings like navigate or click, though it does not explicitly contrast with get_page even though both return page content.

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: an agent can infer this goes after an action that triggers async page changes. There is no explicit statement of when to prefer it over get_page, nor when not to use it, and nothing about what happens if no condition is supplied.

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