Skip to main content
Glama
mcp-cui-chrome

mcp-cui-chrome

by cuipy

悬停

browser_hover

Move the mouse pointer over a referenced element without clicking to reveal hover-only menus and controls.

Instructions

通用:把鼠标移到编号对应的元素上,不点击。用来展开需要悬停才出现的菜单。

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": {
      "ref": "<ref>"
    },
    "name": "browser_hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes元素编号,例如 e4

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.4

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the key behavioral fact that no click occurs, implying the action is non-mutating. It says nothing, though, about whether the element scrolls into view, whether the tool waits for the hover effect, what the response contains, or how an invalid ref fails.

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 short sentences with zero filler, and the core action plus the non-clicking constraint are front-loaded before the use case. Nothing needs trimming.

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?

For a single-parameter, non-mutating interaction tool with no output schema, the description covers what it does and one motivating scenario. Minor gaps remain around post-hover behavior and failure modes, but an agent can call it correctly from this definition.

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 ref parameter is already documented as an element id with the example e4. The description restates "编号对应的元素" without adding syntax, format, or sourcing detail beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource: move the mouse onto the element identified by ref, and it explicitly adds "不点击" (does not click), which separates it from the obvious sibling browser_click. It falls short of a 5 only because it does not name any sibling outright.

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?

It states a concrete use case: expanding menus that only appear on hover. That tells the agent when this tool is the right choice, but it gives no when-not guidance (e.g. what to do if hovering does nothing) and names no alternatives.

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