DrissionPage-MCP

by hooplus1ce

Overview Schema Source Related Servers Discussions Admin

Python

Local

悬停

element_hover

Hover mouse over a web element to trigger dropdown menus, tooltips, and other hover-dependent UI states.

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": {
      "element_id": "<element_id>"
    },
    "name": "element_hover"
  }
}

Input Schema

Name	Required	Description	Default
`element_id`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A3.9/5.0

Behavior4/5

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

It discloses that the tool triggers hover effects and popups, which is the primary behavioral outcome. It does not mention potential side effects, but none are critical for a hover action.

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 concise sentence that delivers the core information without verbosity or irrelevant details.

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?

The description is sufficiently complete for a hover action with one parameter. It does not mention output or return values, but for a simple UI action this is not a significant gap.

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

Parameters2/5

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

The single parameter element_id is not explained in the description, and the schema provides no additional description. The parameter name is somewhat self-explanatory but the description adds no value to 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 the action (hover) and its purpose (trigger hover effects, tooltips). It is specific to the element_hover tool and distinguishes it from sibling tools like element_click or element_input.

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

Usage Guidelines3/5

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

The description implies usage when hover effects are needed but does not explicitly state when to use or not use this tool compared to alternatives. It lacks explicit when/when-not guidance.

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

Deploy Server

悬停