Skip to main content
Glama

mouse_move

Move the mouse pointer to absolute screen coordinates, letting AI agents and automation position the cursor for clicking or interacting with any app.

Instructions

Move the mouse pointer to absolute screen coordinates.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but discloses almost nothing: it does not say whether motion is instant or animated, whether coordinates are clamped to the screen, what happens on multi-monitor setups, or whether hovering triggers events. Only the absolute-coordinate semantics of the movement are made explicit.

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 zero filler and no redundancy. It is efficient, though the terseness is arguably a symptom of under-specification rather than disciplined editing.

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?

The tool is simple (two required integers, no output schema, no annotations), so the description is close to adequate for basic selection. Missing coordinate origin/units and any note on interaction with mouse_click or hover side effects leave real gaps for an automation tool.

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 0%, but the two parameters are simple integers titled X and Y. The description does add real meaning by specifying that the coordinates are absolute screen positions rather than relative offsets, though it omits origin corner and units (pixels), which matter for correct invocation.

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?

"Move the mouse pointer" names a specific verb and resource, and "absolute screen coordinates" scopes it usefully, implicitly distinguishing it from button-press siblings like mouse_click. It stops short of explicitly differentiating from any named sibling, so it is clear rather than exemplary.

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance, no mention of how this relates to mouse_click (e.g. whether a click follows or requires a move first), and no prerequisites such as whether the pointer events fire on move. Usage must be inferred entirely from the name.

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