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

open-browser-control

by smankoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_request_user

Ask the user to perform a required action like signing in or solving a CAPTCHA. The AI pauses and waits for user confirmation before continuing.

Instructions

Ask the user to perform an action (e.g., sign in, solve CAPTCHA). AI pauses until user signals done.

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": {
      "message": "<message>"
    },
    "name": "browser_request_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesMessage explaining what the user needs to do
timeoutNoAuto-resume after this many ms (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

Description mentions the AI pauses until the user signals done, which is a key behavioral trait. But it lacks details about what happens on timeout, side effects on automation flow, or how the user signals completion. With no annotations, the description carries the full burden and is adequate but not comprehensive.

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?

Two sentences, front-loaded with the core purpose, and no extraneous information. Every phrase earns its place.

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 simple tool with only two parameters and no output schema, the description covers the essential behavioral aspect (pausing). It is complete enough for an agent to use correctly, though it could elaborate on how the user signals done.

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% (both parameters have descriptions). The tool description adds minimal value beyond what the schema provides: it repeats the message usage but does not mention the timeout parameter. Baseline 3 is appropriate.

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?

Clearly states the tool asks the user to perform an action (e.g., sign in, solve CAPTCHA) and that the AI pauses until the user signals done. This verb+resource description distinguishes it well from siblings like browser_click or browser_navigate which perform automated actions.

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?

Implies usage when user input or action is needed (e.g., CAPTCHA, sign-in) and that the AI pauses. However, it does not explicitly state when not to use it or mention alternative tools for automated tasks, leaving room for confusion.

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