Skip to main content
Glama
mcp-cui-chrome

mcp-cui-chrome

by cuipy

拖拽

browser_drag

Drags a starting element onto another element or by pixel offsets to operate sliders, sorting, and other draggable 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": {
      "from": "<from>"
    },
    "name": "browser_drag"
  }
}

Input Schema

NameRequiredDescriptionDefault
dxNo没有 to 时,相对起点向右的像素,向左用负数
dyNo没有 to 时,相对起点向下的像素,向上用负数
toNo拖动终点的元素编号
fromYes拖动起点的元素编号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.4

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the mechanics of both drag modes ('hold an element, drag onto another, or drag by pixel offset'). It does not mention preconditions (element must be visible/scrolled into view), waiting behavior, or failure modes when an element reference is invalid.

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?

Two short sentences, front-loaded with the general capability followed by concrete use cases; nothing is padding. The '通用:' prefix is slightly redundant but harmless.

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 4-parameter tool with no annotations and no output schema, the description covers purpose, both modes, and typical use cases adequately. Remaining gaps (element-not-found handling, whether the element is auto-scrolled into view) are minor for an atomic browser interaction.

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%, and the schema already explains that dx/dy apply only when 'to' is absent and that negative values move left/up. The description adds no parameter-level detail beyond that, so the baseline of 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 names a concrete verb+resource (press-and-hold an element and drag it) and enumerates the two operating modes: onto another element, or by pixel offset. The use-case list (sliders, sorting, drag-required controls) implicitly separates it from browser_click/browser_hover, though it never names those siblings.

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?

It lists scenarios where dragging is the right interaction (sliders, sorting, drag controls), which gives implied usage context. There is no explicit when-not guidance or named alternative such as browser_click for simple activation, so guidance remains inferential.

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