Skip to main content
Glama

desktop_mouse_move

Moves the mouse cursor to absolute screen coordinates so you can target UI elements by position in headed desktop automation sessions.

Instructions

agent-desktop mouse-move: Move cursor to absolute screen coordinates (requires --headed)

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": {
      "xy": "<xy>"
    },
    "name": "desktop_mouse_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
xyYesAbsolute coordinates as x,y; requires --headed; write a negative value with = (--xy=-100,50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/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 behavioral burden; it does disclose the important '--headed' prerequisite twice, which is real value. However it is silent on whether the move is instantaneous, whether it fires hover events, how multi-display coordinates are interpreted, and what the call returns.

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?

A single front-loaded sentence with the tool prefix and the precondition included; nothing is padded. The 'agent-desktop mouse-move:' prefix is slightly redundant with the tool name, which keeps it from a 5.

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 one-parameter tool with full schema coverage and no output schema, the essentials are present via the schema plus the --headed caveat. Missing is any statement of effect or return (does it just reposition, does it emit events), which matters because no annotations exist to cover that.

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% and the schema already documents the 'x,y' string format, the --headed requirement, and the negative-value '=' syntax. The description adds no syntax or format detail beyond that, so baseline 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 states a specific verb and object ('Move cursor') plus a scope ('absolute screen coordinates'), which is enough to distinguish this from siblings like desktop_mouse_click or desktop_drag. It stops short of naming an alternative for relative movement, but the operation itself 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is the precondition 'requires --headed', which is useful but is a capability constraint rather than a when-to-use rule. It never says to prefer this over desktop_hover/desktop_drag or what to do if a headed session is unavailable, so selection guidance is implied at best.

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