Skip to main content
Glama

pilot_resume

Resume browser automation control after manual intervention by capturing a fresh page state snapshot for continued AI-driven task execution.

Instructions

Resume control after user handoff. Takes a fresh snapshot of the current page state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The registration and handler implementation for the 'pilot_resume' MCP tool.
    server.tool(
      'pilot_resume',
      'Resume control after user handoff. Takes a fresh snapshot of the current page state.',
      {},
      async () => {
        await bm.ensureBrowser();
        try {
          await bm.resume();
          const { takeSnapshot } = await import('../snapshot.js');
          const snapshot = await takeSnapshot(bm, { interactive: true });
          return { content: [{ type: 'text' as const, text: `RESUMED\n${snapshot}` }] };
        } catch (err) {
          return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
        }
Behavior2/5

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

With no annotations provided, the description carries full disclosure burden. While it mentions 'takes a fresh snapshot' (revealing a read-like side effect), it fails to explain what 'resume control' entails mechanistically, potential failure modes if called without prior handoff, or whether this mutates any internal automation state.

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 tightly constructed sentences with zero waste. The first sentence states the core purpose immediately (front-loaded), while the second adds necessary behavioral detail about the snapshot. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a zero-parameter tool with no output schema, covering the basic action and immediate result. However, given the rich sibling ecosystem (including pilot_handoff and multiple snapshot variants), the description should elaborate on the handoff/resume lifecycle relationship and what specific control is being resumed.

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?

Input schema has zero parameters, which per calibration establishes a baseline of 4. The description adds the detail that it 'takes a fresh snapshot', providing semantic context for what the tool produces despite having no formal input parameters to describe.

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 uses a specific verb ('Resume') with clear resource ('control') and contextual scope ('after user handoff'), which effectively distinguishes this from sibling 'pilot_handoff'. However, it stops short of explicitly naming the sibling tool or explicitly stating this is the inverse operation.

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?

Provides implicit usage context by stating 'after user handoff', suggesting when to invoke this tool. However, it lacks explicit prerequisites (e.g., 'only call after pilot_handoff'), exclusions, or alternatives that would help an agent understand when NOT to use this versus other navigation tools.

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