Skip to main content
Glama

tab_wait

Waits for specified text to appear or, if gone is set, disappear on a browser page, then returns matching lines with refs. Use for delayed results, loading messages, or login steps.

Instructions

Wait until a text shows on a page in the user's browser, or with gone until it no longer does: a result that loads after a delay, a loading message going away, or the user finishing a step you asked them to do, such as logging in. Returns the lines that mention the text, with refs, as tab_find does. Does not touch the page.

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": {
      "text": "<text>"
    },
    "name": "tab_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
goneNoWait until the text no longer shows, such as a "Loading" message. Defaults to false.
textYesText to wait for, case-insensitive, as tab_find matches it: part of a label, a button name, a heading.
tabIdNoTab id from tab_list or tab_read. Defaults to the active tab of the browser window the user used last.
timeoutSecondsNoHow long to wait. Defaults to 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key traits: it blocks waiting, it is non-mutating ('Does not touch the page'), and it returns matching lines with refs in the same shape as tab_find. The notable omission is what happens when the wait expires (error vs. empty result), which matters for a timeout-bounded blocking tool.

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?

Effectively three sentences, front-loaded with the core action before the examples and the return/read-only caveats. The 'or with gone until it no longer does' clause is slightly convoluted, but no sentence is wasted.

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 4-parameter, no-output-schema, no-annotation tool, the description covers purpose, triggering context, return shape, and non-mutation. Only the timeout failure behavior and whether it polls the page are left unstated, which are minor gaps against otherwise strong coverage.

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% and every parameter is documented there, including 'gone' semantics, case-insensitivity, tabId provenance, and the 30s/300s timeout bounds. The description reinforces the 'gone' mode with an example ('a loading message going away') but adds no syntax or behavior beyond the schema, so the 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?

States a specific verb and resource ('Wait until a text shows on a page in the user's browser') plus the inverse mode via 'gone', which no sibling tab_* tool provides. It also explicitly distinguishes itself from retrieval siblings by saying it returns lines with refs 'as tab_find does' and that it 'Does not touch the page'.

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?

Gives three concrete trigger scenarios: a result loading after a delay, a loading message disappearing, and the user finishing a step you asked for such as logging in. These make the when-to-use condition clear. It does not state the negative case, e.g. use tab_find instead when the text is likely already present, so it stops short of explicit alternatives.

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