Skip to main content
Glama

wait_for_user

Hands a shared browser tab to the user and waits for confirmation, enabling CAPTCHAs, 2FA codes, logins, payments, or user choices. Returns when they press Done or Resume, or after the timeout.

Instructions

Hand a shared tab to the user and wait for them. With message, the page shows it with a Done button and brings the tab to the front: use it for CAPTCHAs, 2FA codes, logins, payment confirmation or any choice that is theirs. Without message, it waits for the user to resume a tab they paused (actions on a paused tab fail with a note saying so). Returns when they press Done or Resume, or after the timeout.

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_for_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.
messageNoWhat the user should do, in one or two sentences.
timeout_secondsNoDefault 300, at most 900.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the UI side effect (page shows the message with a Done button and the tab is brought to the front), the termination conditions (Done, Resume, or timeout), and the paused-tab side effect that makes other actions fail. The remaining gap is what the call yields on return — no output schema exists, so the agent cannot tell whether user input or just a status comes back.

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?

Three tight sentences front-load the action, then branch into the two modes, then state the return conditions. Parenthetical asides are short and each carries operational information rather than filler.

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 handoff tool with no annotations and no output schema, the description covers activation, side effects, blocking behavior, and exit conditions. The one thing an agent would still want — the shape of the returned result after Done/Resume/timeout — is absent, and nothing else fills that role.

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%, so the baseline is 3. The description does add meaning beyond the schema by contrasting behavior with and without 'message' (prompt-with-Done versus resume-a-paused-tab), which is the key semantic decision the agent must make; the tab handle and timeout values themselves are left to the schema.

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 concrete verb and resource ('Hand a shared tab to the user and wait'), and the two operating modes are spelled out: with message it presents a prompt and foregrounds the tab; without message it waits for the user to resume a paused tab. This is clearly distinct from sibling waits like wait_for and wait_for_download, which do not involve human handoff.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger conditions tied to real situations: CAPTCHAs, 2FA codes, logins, payment confirmation, or 'any choice that is theirs'. It also covers the alternative mode (no message, resuming a paused tab) and warns that actions on a paused tab fail with an explanatory note, so the agent knows both when to call it and what state it implies.

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