Skip to main content
Glama
linux-computer-use-mcp

linux-computer-use-mcp

by dhakseshr

drag

Moves windows, sliders, and selections by pressing at a start point, gliding to an end point, and releasing the mouse button.

Instructions

Press at the start point, glide to the end point, release. For moving windows, sliders, selections.

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": "drag"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_xYes
end_yYes
buttonNoleft
start_xYes
start_yYes
screenshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the whole behavioral load; it does disclose the press-glide-release interaction model, which tells the agent a button is held for the duration of a single continuous gesture. It says nothing about timing/interpolation, whether the call blocks until release, what happens on failure mid-drag, or that a screenshot is captured by default.

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, with the gesture sequence front-loaded before the use cases, and no filler. The second sentence is a terse fragment but is informative rather than redundant.

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?

For a six-parameter input-device tool with zero schema documentation, no annotations, and no output schema, the definition leaves out coordinate semantics, button behavior, screenshot side effect, and completion/blocking behavior. An agent could call it, but not confidently predict what it will do or how to interpret results.

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?

Schema description coverage is 0% across six parameters, so the description must compensate and only partly does: 'start point' and 'end point' map to start_x/start_y and end_x/end_y. Nothing explains the coordinate frame (screen-absolute vs window-relative), the 'button' enum choice, or the 'screenshot' flag, which are the two parameters an agent is most likely to get wrong.

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 gesture ('Press at the start point, glide to the end point, release') and names the resources it acts on (windows, sliders, selections), which separates it from sibling primitives like click or move_mouse. It stops short of explicitly naming an alternative, so it is clear but not fully differentiated.

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?

'For moving windows, sliders, selections' gives concrete scenarios where a drag is the right call, which is real selection guidance rather than an implied one. It provides no exclusions or explicit pointer to click/move_mouse for cases where no drag is needed.

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