Skip to main content
Glama
Sign In
Computer Use MCP Server

Computer Use MCP Server

by SebastianBaltes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

computer_left_click_drag

Performs a click-and-drag action from start to end coordinates on the Linux X11 desktop. Use for drag-and-drop, resizing windows, or selecting text regions.

Instructions

Click and drag from start coordinates to end coordinates. Useful for drag-and-drop, resizing windows, selecting text regions, etc. The display is 1429x804 pixels (scaled from 1920x1080). All coordinates are in the scaled coordinate space.

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": {
      "start_x": "<start_x>",
      "start_y": "<start_y>",
      "end_x": "<end_x>",
      "end_y": "<end_y>"
    },
    "name": "computer_left_click_drag"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_xYesStart X coordinate
start_yYesStart Y coordinate
end_xYesEnd X coordinate
end_yYesEnd Y coordinate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It mentions display resolution and coordinate space, but does not detail mouse button behavior (e.g., whether it presses and holds, if it moves to start first, or if it releases at end). For a drag operation, these are significant gaps.

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 efficient sentences. First sentence states action and use cases, second provides display context. No extraneous information.

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

Completeness2/5

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

Without an output schema, the agent is left wondering about return value (presumably none) and behavioral details like whether the mouse is moved to start first or if the button is released. For a drag tool, these are important for correct invocation.

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% with each parameter having a clear description (e.g., 'Start X coordinate'). The description adds only the note about scaled coordinate space, which is helpful but minor. Baseline 3 is appropriate.

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 'Click and drag from start coordinates to end coordinates' and provides specific use cases (drag-and-drop, resizing, selecting text). It distinguishes from siblings like computer_left_click and computer_mouse_move by specifying the drag action.

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?

The description gives examples of when to use the tool (drag-and-drop, resizing, selecting text), which helps guide usage. However, it does not explicitly state when not to use it or compare to alternatives.

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