Skip to main content
Glama
Wladastic

AutoProbeMCP

by Wladastic
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

close_browser

Terminate the active browser instance in AutoProbeMCP to end web interactions and free resources during browser automation tasks.

Instructions

Close the current browser instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:654-679 (handler)
    Handler implementation for the close_browser tool. Closes the current browser instance if it exists, resets global browser state variables, and returns a success or no-browser message.
    case 'close_browser': {
  if (currentBrowser) {
    await currentBrowser.close();
    currentBrowser = null;
    currentContext = null;
    currentPage = null;

    return {
      content: [
        {
          type: 'text',
          text: 'Browser closed successfully'
        }
      ]
    };
  } else {
    return {
      content: [
        {
          type: 'text',
          text: 'No browser instance to close'
        }
      ]
    };
  }
}
  • src/index.ts:322-329 (registration)
    Registration of the close_browser tool in the ListToolsRequestHandler, defining its name, description, and empty input schema.
    {
  name: 'close_browser',
  description: 'Close the current browser instance',
  inputSchema: {
    type: 'object',
    properties: {}
  }
},

Tool Definition Quality

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action but doesn't disclose behavioral traits such as whether this is destructive (likely yes, as closing terminates the instance), if it requires specific conditions (e.g., browser must be launched first), or what happens post-closure (e.g., resources freed).

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, clear sentence with zero waste—it directly states the tool's purpose without fluff. It's front-loaded and appropriately sized for a simple action with no parameters.

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?

Given the tool's low complexity (0 parameters, no output schema) and lack of annotations, the description is minimally adequate. It states what the tool does but lacks completeness in behavioral context (e.g., effects, prerequisites) that would help an agent use it correctly in workflows with siblings.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately doesn't mention parameters, aligning with the schema. Baseline is 4 for zero parameters, as it avoids unnecessary details.

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?

The description 'Close the current browser instance' clearly states the action (close) and the resource (current browser instance) with specific terminology. It distinguishes from siblings like 'launch_browser' (creation vs. termination) and 'navigate' (interaction vs. shutdown).

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?

The description implies usage context by specifying 'current browser instance', suggesting it should be used when a browser is already open. However, it lacks explicit guidance on when to use it versus alternatives (e.g., after completing tasks) or prerequisites (e.g., requires an active browser).

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

Related 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/Wladastic/AutoProbeMCP'

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