Skip to main content
Glama
enesjakozh
dragons96

MCP-Undetected-Chromedriver

by dragons96
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

browser_go_forward

Navigate forward in browser history using Chrome automation, bypassing anti-bot detection for seamless web scraping and testing workflows in restricted environments.

Instructions

Navigate forward in browser history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/mcp_server_undetected_chromedriver/server.py:352-362 (handler)
    The handler function for the 'browser_go_forward' tool. It is decorated with @mcp.tool() for registration. It ensures the browser is available, executes driver.forward() to navigate forward in history, and returns a success response.
    @mcp.tool()
async def browser_go_forward():
    """Navigate forward in browser history"""

    async def go_forward_handler(driver: uc.Chrome):
        driver.forward()
        return await create_success_response("Navigated forward in browser history")

    return await tool.safe_execute(
        ToolContext(webdriver=await ensure_browser()), go_forward_handler
    )

Tool Definition Quality

B3.1/5.0
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. It states the action but doesn't disclose what happens when no forward history exists (error? no-op?), whether it waits for page load, or any side effects. For a navigation tool with zero annotation coverage, this leaves significant gaps.

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 wasted words. It's front-loaded with the core action and resource, making it immediately understandable without unnecessary elaboration.

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?

Given the tool's behavioral complexity (navigation with potential state dependencies) and absence of both annotations and output schema, the description is insufficient. It doesn't explain what the tool returns, error conditions, or interaction with browser state, leaving the agent with incomplete operational understanding.

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% (though empty). The description appropriately doesn't discuss parameters since none exist, which is correct for this case. Baseline for zero parameters is 4.

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 ('Navigate forward') and resource ('browser history'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'browser_go_back', which performs the opposite navigation action in history.

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. The description doesn't mention prerequisites (like requiring forward history to exist) or compare it to other navigation methods like 'browser_navigate' for direct URL access.

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