Skip to main content
Glama
Sign In
DrissionPage-MCP

DrissionPage-MCP

by hooplus1ce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

悬停单元格读取颜色

vtable_hover_cell
Read-only

Hover over a table cell to retrieve its background and text colors, detect interactive text (links, pointer, underline), and check neighbor cell backgrounds for row highlighting.

Instructions

真实鼠标悬停在单元格上（自动滚动到位），读取悬停态颜色信息： 单元格背景色、文本颜色、是否可交互文本（link/cursor:pointer/下划线） 及同行邻格背景（用于检测行高亮）。

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": {
      "col": "<col>",
      "row": "<row>"
    },
    "name": "vtable_hover_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
colYes
rowYes
tab_idNo
table_indexNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

The description discloses key behavioral details: it uses a 'real mouse' hover and 'auto-scrolls' into view. This goes beyond the readOnlyHint annotation by explaining the action mechanism. However, it does not mention potential side effects like moving the mouse pointer or triggering hover effects, though readOnlyHint covers the main safety aspect.

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 a single sentence but dense and free of fluff. It is well-structured and directly mentions the key facts. It could benefit from a bullet list for the output items, but overall it is concise and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool's purpose and behavior are described, but critical context is missing: coordinate system (0-based vs 1-based), expected return format, and behavior when the cell is not found. Since an output schema exists, the return format may be covered there, but the description alone leaves some gaps for a tool that requires precise cell coordinates.

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

Parameters1/5

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

The schema has 4 parameters with 0% description coverage, and the description does not explain col, row, tab_id, or table_index. It mentions 'cell' and 'same-row neighbor' but never specifies coordinate systems, indexing, or the meaning of the optional parameters. Since the schema provides no help, the description fails to compensate, leaving the agent with insufficient parameter guidance.

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 tool's action: real mouse hover on a cell (with auto-scroll) to read hover-state color information. It lists specific outputs (background color, text color, interactive text status, row highlighting) and distinguishes itself from sibling tools like vtable_read_cells or vtable_cell_info by focusing on hover states.

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 explains what the tool does but does not explicitly indicate when to use it over alternatives. There is no mention of 'use this when you need hover colors' or 'instead of vtable_cell_info'. The purpose is clear but the selection guidance is only implicit.

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

Deploy Server

Other Tools