Skip to main content
Glama
nfodor

Chromium ARM64 Browser

by nfodor

close_browser

Terminates the Chromium browser instance to free system resources on ARM64 devices after completing automation tasks or web testing workflows.

Instructions

Close the browser instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core implementation of the close_browser MCP tool. Closes WebSocket connection, terminates Chromium process with graceful shutdown handling, resets globals, and returns success response.
    async closeBrowser() {
      if (wsConnection) {
        wsConnection.close();
        wsConnection = null;
      }
      
      if (chromiumProcess && chromiumProcess.exitCode === null) {
        chromiumProcess.kill('SIGTERM');
        
        // Wait for graceful shutdown
        await new Promise(resolve => {
          chromiumProcess.on('exit', resolve);
          setTimeout(() => {
            chromiumProcess.kill('SIGKILL');
            resolve();
          }, 5000);
        });
        
        chromiumProcess = null;
      }
      
      currentTabId = null;
      
      return {
        content: [{ type: 'text', text: 'Browser closed successfully' }],
      };
    }
  • index.js:336-342 (registration)
    Registers the close_browser tool in the ListTools response, including its name, description, and empty input schema.
      name: 'close_browser',
      description: 'Close the browser instance',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Implementation of close_browser in the browser-only MCP server variant. Closes connection and process, resets state.
    async closeBrowser() {
      if (wsConnection) {
        wsConnection.close();
        wsConnection = null;
      }
      
      if (chromiumProcess) {
        chromiumProcess.kill('SIGTERM');
        chromiumProcess = null;
      }
      
      currentTabId = null;
      
      return {
        content: [{ type: 'text', text: 'Browser closed successfully' }],
      };
    }
  • Tool registration for close_browser in the browser-only server, with schema definition.
    {
      name: 'close_browser',
      description: 'Close the browser instance',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. 'Close the browser instance' implies a destructive action that terminates the session, but it doesn't specify whether this is reversible, what happens to open tabs/data, or if authentication is affected. For a potentially destructive tool with zero annotation coverage, this is inadequate.

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?

The description is a single, direct sentence with no wasted words. It's front-loaded with the core action and resource, making it immediately understandable. Every word earns its place.

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 tool that likely terminates a browser session (a significant action), the description is insufficient given no annotations or output schema. It doesn't explain what 'close' entails (e.g., graceful shutdown, data loss), return values, or error conditions. The simplicity of having no parameters doesn't compensate for the lack of behavioral context.

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?

The tool has zero parameters, and schema description coverage is 100% (empty schema). The description doesn't need to explain parameters, so it meets baseline expectations. No parameter information is missing or needed.

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 clearly states the action ('Close') and resource ('the browser instance'), making the purpose immediately understandable. It doesn't distinguish from siblings like 'navigate' or 'get_content', but the verb+resource combination is specific enough for basic understanding.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus alternatives. While the action is self-explanatory, there's no mention of prerequisites (e.g., must have an active browser session) or consequences (e.g., losing current page state). The description assumes context without providing it.

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/nfodor/mcp-chromium-arm64'

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