Skip to main content
Glama
LukeLamb

claude-linux-mcp

mouse_drag

Destructive

Perform a mouse drag from start to target coordinates, with optional button selection (left, middle, or right).

Instructions

Drag from (x1, y1) to (x2, y2) while holding the given button (default left).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
x1Yes
y1Yes
x2Yes
y2Yes
buttonNoDefault: left.
Behavior4/5

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

The description adds behavioral detail beyond the destructiveHint annotation by specifying the exact gesture (drag from one point to another while holding a button).

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?

One concise sentence, front-loaded with the verb 'Drag', no redundancy.

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?

Lacks details on coordinate system, return value, or error conditions; given moderate complexity and no output schema, more context would help.

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?

With only 20% schema coverage, the description compensates minimally; it contextualizes x1,y1,x2,y2 as start/end points but does not clarify units, coordinate system, or provide further detail.

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 'Drag' from (x1,y1) to (x2,y2) with an optional button, distinguishing it from siblings like mouse_click, mouse_move, etc.

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?

Usage is implied by the name and description, but there is no explicit guidance on when to use this tool versus alternatives like mouse_drag vs mouse_move or mouse_click.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LukeLamb/claude-linux-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server