Skip to main content
Glama

macos_mouse_move

Move the macOS mouse cursor to an absolute screen position in logical points, enabling precise desktop automation and pointer placement outside the browser.

Instructions

macOS only. Move the mouse cursor to an absolute position in logical coordinates (macOS points, top-left origin), read off macos_screen_capture or macos_mouse_current_position. Inside the browser, tab_click targets page elements exactly instead. Requires Accessibility permission.

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

Input Schema

NameRequiredDescriptionDefault
xYesAbsolute X coordinate in logical points (top-left origin).
yYesAbsolute Y coordinate in logical points (top-left origin).
smoothNoInterpolate the movement over ~300ms instead of teleporting. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the platform restriction, the coordinate convention that governs correctness, and the Accessibility permission prerequisite. It stops short of describing failure behavior (e.g., what happens if permission is not granted or the point is off-screen) or whether the call returns anything, which is the remaining gap.

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?

Four short sentences, each doing distinct work: platform gate, coordinate model, alternative routing, permission prerequisite. Front-loaded with platform and action, no filler.

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

Completeness4/5

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

For a 3-parameter, no-annotation, no-output-schema tool, the description covers platform, coordinate semantics, prerequisite, and the in-browser alternative. The only omission is error/permission-failure behavior, which is minor for a simple positioning call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds meaning beyond the schema by telling the agent where to read coordinate values from (macos_screen_capture, macos_mouse_current_position) and that coordinates are absolute rather than cursor-relative. The smooth parameter is not discussed in the description, only in the schema.

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?

Specific verb+resource ('Move the mouse cursor to an absolute position') with the coordinate model spelled out (macOS logical points, top-left origin). It also explicitly distinguishes itself from tab_click for in-browser targeting, so an agent can pick the right tool without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-to-use (absolute positioning in logical coordinates) and when-not (inside the browser, use tab_click for page elements), plus a concrete way to obtain the inputs from macos_screen_capture or macos_mouse_current_position. The prerequisite (Accessibility permission) is stated up front.

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