Skip to main content
Glama

pilot_close

Close the browser and clean up resources to manage memory and end automation sessions.

Instructions

Close the browser and clean up all resources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implementation of the 'pilot_close' tool handler, which closes the browser managed by `bm`.
    server.tool(
      'pilot_close',
      'Close the browser and clean up all resources.',
      {},
      async () => {
        try {
          await bm.close();
          return { content: [{ type: 'text' as const, text: 'Browser closed.' }] };
        } catch (err) {
          return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
        }
      }
    );
Behavior3/5

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

No annotations are provided, so the description carries full disclosure burden. It mentions 'clean up all resources' which provides some behavioral context, but lacks specifics on reversibility, what resources are cleaned (memory, disk, temp files), or side effects on other operations.

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?

Seven words across two clauses with zero redundancy. 'Close the browser' delivers the core action immediately; 'clean up all resources' adds necessary scope qualification without verbosity.

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 zero-parameter cleanup tool without output schema, the description adequately covers the operation. A minor gap exists regarding whether this is a final terminal operation or recoverable, but sufficient for tool selection.

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 contains zero parameters. Per evaluation rules, zero-parameter tools establish a baseline score of 4.

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?

Description uses specific verb 'Close' with explicit resource 'browser', distinguishing it from sibling 'pilot_tab_close'. The addition of 'clean up all resources' clarifies scope beyond just window closing.

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?

While the description implicitly contrasts with tab-level operations via 'browser' scope, it does not explicitly state when to use this versus 'pilot_tab_close' or warn that this terminates the entire session.

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