Skip to main content
Glama

pilot_handoff

Switch to visible Chrome to manually solve CAPTCHAs, bypass bot detection, or complete complex authentication, then resume automated browsing.

Instructions

Open a visible (headed) Chrome window with all current state — cookies, tabs, localStorage. Use when headless mode is blocked by CAPTCHAs, bot detection, or complex auth. The user can solve it manually, then call pilot_resume to continue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implementation of the 'pilot_handoff' tool handler. It calls `bm.handoff()` to open a visible browser.
    server.tool(
      'pilot_handoff',
      'Open a visible (headed) Chrome window with all current state — cookies, tabs, localStorage. Use when headless mode is blocked by CAPTCHAs, bot detection, or complex auth. The user can solve it manually, then call pilot_resume to continue.',
      {},
      async () => {
        await bm.ensureBrowser();
        try {
          const result = await bm.handoff();
          return { content: [{ type: 'text' as const, text: result }] };
        } catch (err) {
          return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
        }
      }
    );
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses state preservation (cookies/tabs/localStorage), UI visibility change (headed), human-in-the-loop requirement (user solves manually), and session continuity mechanism (pilot_resume). Minor gap: doesn't clarify if this spawns parallel browser or mutates existing session.

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 sentences with zero waste: (1) Function definition, (2) Trigger condition, (3) Post-action workflow. Perfect front-loading of critical behavioral info (headed vs headless) in the opening clause.

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?

Given zero parameters and no output schema, the description excellently covers the tool's role in the broader workflow (handoff/resume cycle). Mentions sibling tool pilot_resume. Slight gap: doesn't specify return value, though this is less critical for a control-flow tool.

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

Parameters4/5

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

Zero parameters present (empty properties object), meeting the baseline score of 4 per rubric. Description appropriately requires no parameter explanation.

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?

Excellent specificity: 'Open a visible (headed) Chrome window' provides clear verb + resource, and 'with all current state — cookies, tabs, localStorage' defines scope. It distinguishes from headless automation siblings by explicitly defining the 'headed' mode use case.

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?

Explicit conditional usage: 'Use when headless mode is blocked by CAPTCHAs, bot detection, or complex auth.' Also names the exact follow-up tool ('call pilot_resume to continue'), creating clear workflow guidance relative to siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TacosyHorchata/Pilot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server