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

linux-computer-use-mcp

by dhakseshr

move_mouse

Move the pointer to specific x,y coordinates without clicking, letting you hover over elements to reveal tooltips or open menus during desktop automation.

Instructions

Move the pointer to x,y without clicking (hover to reveal tooltips or menus).

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "move_mouse"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
screenshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; it usefully discloses that no click occurs and that hovering is the intent. It says nothing about the coordinate frame (screen vs. window-relative), whether the target window must be foregrounded, or any failure behavior.

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?

A single front-loaded sentence with the action first and the rationale in parentheses; every clause earns its place and nothing is padded.

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?

For a simple pointer-movement tool the core action is covered, but the undocumented screenshot flag and unspecified coordinate system leave real gaps, especially since there is no output schema to explain what the call returns.

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 coverage is 0%, so the description must compensate, but it only weakly implies what x and y mean (a move target) without specifying the coordinate origin. The third parameter, screenshot (default true), is not mentioned at all, leaving its effect on the response undocumented.

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?

States a specific verb and resource ("Move the pointer to x,y") plus the distinguishing behavior "without clicking," which separates it from the click sibling. It stops short of naming an alternative tool, but the action is unambiguous.

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?

Gives concrete usage context ("hover to reveal tooltips or menus") and implicitly routes clicking actions elsewhere via "without clicking." No explicit exclusions or prerequisite conditions are stated, such as needing the target window focused.

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