Skip to main content
Glama
dragons96

MCP-Undetected-Chromedriver

by dragons96

browser_hover

Simulate mouse hover over a specified webpage element using a CSS selector. Designed for automated web interactions with Chrome while evading bot detection mechanisms.

Instructions

Hover over an element on the page

Args:
    selector: CSS selector for element to hover over - required

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYes

Implementation Reference

  • The handler function for 'browser_hover' tool. It is registered via @mcp.tool() decorator. Takes a CSS selector, finds the element using Selenium, performs a hover action using ActionChains, and returns a success response.
    @mcp.tool()
    async def browser_hover(
            selector: str,
    ):
        """Hover over an element on the page
    
        Args:
            selector: CSS selector for element to hover over - required
        """
        assert selector, "Selector is required"
    
        async def hover_handler(driver: uc.Chrome):
            element = driver.find_element(By.CSS_SELECTOR, selector)
            ActionChains(driver).move_to_element(element).perform()
            return await create_success_response(f"Hovered over {selector}")
    
        return await tool.safe_execute(
            ToolContext(webdriver=await ensure_browser()), hover_handler
        )
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 of behavioral disclosure. It only states the action ('hover over') without mentioning potential side effects (e.g., UI changes, network requests), error conditions, or what happens if the selector is invalid. This leaves significant gaps for a tool that interacts with a browser.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action ('Hover over an element on the page') and efficiently includes parameter details in a separate section. It avoids unnecessary words, though the formatting with 'Args:' could be slightly more integrated.

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 complexity of browser interactions and the lack of annotations or output schema, the description is incomplete. It doesn't cover behavioral aspects like what the hover action entails, potential outcomes, or error handling, which are crucial for safe and effective use in a browser automation context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning by explaining that the 'selector' parameter is a 'CSS selector for element to hover over - required', which clarifies its purpose beyond the schema's basic type. However, with 0% schema description coverage and only one parameter, this is adequate but minimal, meeting the baseline for such a simple case.

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 verb ('hover over') and resource ('an element on the page'), making the purpose immediately understandable. It distinguishes itself from siblings like browser_click or browser_press_key by specifying the hover action, though it doesn't explicitly contrast with them.

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 on when to use this tool versus alternatives. While the description implies it's for hovering over elements, it doesn't specify scenarios where hovering is appropriate (e.g., triggering dropdowns or tooltips) or when other tools like browser_click might be better.

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