Skip to main content
Glama
dragons96

MCP-Undetected-Chromedriver

by dragons96

browser_close

Close and release resources from a Chrome browser session controlled by the MCP-Undetected-Chromedriver server, ensuring clean termination for web scraping, testing, and automation tasks.

Instructions

Close the browser and release all resources

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'browser_close' tool. It calls reset_browser_state() to quit the webdriver and returns a success response.
    @mcp.tool()
    async def browser_close():
        """Close the browser and release all resources"""
        await reset_browser_state()
        return await create_success_response("Browser closed successfully")
  • Helper function that quits the global webdriver instance and sets it to None.
    async def reset_browser_state():
        if Global.webdriver:
            Global.webdriver.quit()
            Global.webdriver = None
  • Helper function to create a successful CallToolResult response.
    async def create_success_response(message: str | list[str]) -> types.CallToolResult:
        if isinstance(message, str):
            message = [message]
        return types.CallToolResult(
            content=[TextContent(type="text", text=msg) for msg in message],
            isError=False,
        )
  • The @mcp.tool() decorator registers the browser_close function as an MCP tool.
    @mcp.tool()
    async def browser_close():
        """Close the browser and release all resources"""
        await reset_browser_state()
        return await create_success_response("Browser closed successfully")
Behavior3/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 discloses the behavioral trait of releasing resources, which is useful context beyond just closing. However, it does not mention side effects like ending all active sessions or whether the action is reversible.

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, efficient sentence with zero waste. It is front-loaded with the core action and includes necessary additional context ('release all resources') without redundancy.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is mostly complete. It explains the action and resource release, but could benefit from mentioning irreversible effects or typical usage scenarios to fully guide an agent.

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 0 parameters with 100% schema description coverage, so no parameter information is needed. The description does not add parameter details, which is appropriate, earning a baseline score of 4 for this context.

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 clearly states the specific action ('Close') and resource ('the browser'), distinguishing it from sibling tools like browser_navigate or browser_screenshot. It precisely communicates the tool's function without ambiguity.

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

Usage Guidelines4/5

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

The description implies usage context—closing the browser when done with browsing tasks—but does not explicitly state when to use it versus alternatives or prerequisites. It lacks explicit exclusions or comparisons to sibling 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

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/dragons96/mcp-undetected-chromedriver'

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