mcp-chromium-cdp

Overview Schema Source Related Servers Discussions Admin

chrome_hover

Hover over an element using a CSS selector to trigger React synthetic hover events, enabling dropdowns and tooltips to appear before clicking in single-page applications.

Instructions

Hover over an element using a CSS selector. Essential for React SPAs where hover activates synthetic event handlers. Use before chrome_click when dealing with dropdowns, tooltips, or interactive elements that require hover state.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "selector": "<selector>"
    },
    "name": "chrome_hover"
  }
}

Input Schema

Name	Required	Description	Default
`selector`	Yes	CSS selector for the element to hover

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that hover activates synthetic event handlers in React SPAs, providing useful context. However, it does not mention potential side effects, error handling, or whether the action is synchronous, leaving some gaps for a tool with no annotation support.

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?

Two concise sentences: the first states the core action, the second provides usage context. No fluff or redundancy, making it efficient and easy to parse.

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 simplicity (1 param, no output schema), the description covers the essential purpose and usage scenario. It could improve by noting error behavior or return value, but for a hover action, the provided context is sufficient for an agent to select and invoke the tool correctly.

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 coverage is 100%: the only parameter 'selector' is fully described as 'CSS selector for the element to hover.' The description repeats 'CSS selector' without adding extra syntax, constraints, or examples, so it adds no value beyond the schema.

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 'Hover over an element using a CSS selector' with a specific verb and resource. It also distinguishes the tool from chrome_click by explaining when hover should precede click, which aligns with its role among sibling tools.

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

Usage Guidelines5/5

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

Explicitly describes when to use: 'Essential for React SPAs where hover activates synthetic event handlers' and 'Use before chrome_click when dealing with dropdowns, tooltips, or interactive elements that require hover state.' This provides clear context and directly references an alternative tool (chrome_click).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.