Skip to main content
Glama
Rainmen-xia

Chrome Debug MCP Server

by Rainmen-xia

hover

Simulate mouse hover at specified coordinates in Chrome for browser automation and debugging tasks.

Instructions

将鼠标悬停在指定坐标位置

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coordinateYes悬停位置的坐标,格式为 'x,y'

Implementation Reference

  • The main handler function for the 'hover' tool. It moves the mouse to the specified coordinate using Puppeteer, applies a small delay for hover effects, and includes network activity monitoring via handleMouseInteraction.
    async hover(coordinate: string): Promise<BrowserActionResult> {
    	return this.doAction(async (page) => {
    		await this.handleMouseInteraction(page, coordinate, async (x, y) => {
    			await page.mouse.move(x, y);
    			// 小延迟以允许任何悬停效果出现
    			await delay(300);
    		});
    	});
    }
  • The schema definition for the 'hover' tool in the tool list response, defining the input parameter 'coordinate' as a string in 'x,y' format.
    {
    	name: "hover",
    	description: "将鼠标悬停在指定坐标位置",
    	inputSchema: {
    		type: "object",
    		properties: {
    			coordinate: {
    				type: "string",
    				description: "悬停位置的坐标,格式为 'x,y'",
    			},
    		},
    		required: ["coordinate"],
    	},
    },
  • src/index.ts:211-216 (registration)
    The dispatch logic in the CallToolRequestSchema handler that routes 'hover' tool calls to the browserSession.hover method, including input validation.
    case "hover":
    	if (!args?.coordinate) {
    		throw new Error("coordinate参数是必需的");
    	}
    	result = await this.browserSession.hover(args.coordinate as string);
    	break;
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 what the tool does but doesn't disclose: whether this requires an active browser session, if it waits for page loads, what happens on invalid coordinates, if it triggers hover events on elements, or any side effects. The description is functionally accurate but lacks operational details needed for safe invocation.

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 in Chinese that directly states the tool's function with zero wasted words. It is front-loaded with the core action ('将鼠标悬停在') and immediately specifies the target. Every part of the sentence earns its place, making it highly concise and well-structured.

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 a browser interaction tool with no annotations and no output schema, the description is incomplete. It doesn't address context like browser state requirements, error conditions, or what constitutes success. Siblings like 'launch_browser' and 'get_page_content' suggest a richer ecosystem that this description doesn't integrate with, leaving gaps for the agent to navigate.

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?

Schema description coverage is 100%, with the parameter 'coordinate' fully documented in the schema as a string in 'x,y' format. The description adds no additional parameter semantics beyond implying coordinate targeting. Since the schema does the heavy lifting, the baseline score of 3 is appropriate—the description doesn't enhance parameter understanding but doesn't detract either.

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 ('将鼠标悬停在' - hover the mouse) and the target ('指定坐标位置' - specified coordinate position). It distinguishes from siblings like 'click' (which performs a click action) and 'type_text' (which inputs text). However, it doesn't explicitly mention the browser/UI context that siblings imply, making it slightly less specific than a perfect 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing an active browser session from 'launch_browser'), when hovering is appropriate versus clicking, or any coordination with other tools like 'get_page_content' for element identification. The agent must infer usage from the tool name alone.

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/Rainmen-xia/chrome-debug-mcp'

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