Skip to main content
Glama

wait_for_human

Read-onlyIdempotent

Pause automated browser flow so a human can complete login, bot check, or 2FA in the visible session, then continue once a specified condition is met.

Instructions

Let a human do a step (login, bot check, 2FA) in the visible browser; wait until a condition holds, then continue in the same session. Only waits.

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

Input Schema

NameRequiredDescriptionDefault
tabIdNo
messageNo
selectorNo
textGoneNo
timeoutMsNo
urlMatchesNo
textMatchesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value by saying the human acts in the visible browser and the session continues afterwards, but it never says what happens on timeout or whether blocking is indefinite.

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?

Two short sentences, front-loaded with the core mechanic and closed with a useful disambiguating fragment. Nothing is padded, though the extreme terseness pushes some necessary detail into other dimensions' gaps.

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 seven-parameter, zero-coverage, no-output-schema tool, the description omits which parameters define the wait condition, how the timeout default of 120000 ms behaves on expiry, and how the 'message' shown to the human is used. What it does cover is the high-level flow only.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across seven parameters, so the description carries the full documentation burden. It only implies that 'a condition' exists, leaving tabId, message, selector, textGone, timeoutMs, urlMatches and textMatches entirely unexplained, including which of the condition parameters are alternatives versus combined.

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 gives a specific verb and object: it pauses the agent while a human performs a step in the visible browser, then resumes on the same session. 'Only waits' explicitly separates it from action-taking siblings like act_fast or batch_actions, though it never names them.

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?

The concrete triggers (login, bot check, 2FA) make it obvious when this tool applies, and 'Only waits' rules out using it to perform the step itself. It stops short of naming an alternative tool or stating what to do when the wait cannot succeed.

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