Skip to main content
Glama

move_mouse

Move the mouse cursor to specific screen coordinates on macOS for desktop automation tasks.

Instructions

Move the mouse cursor to the specified screen coordinates without clicking. Do not narrate visual observations or coordinate calculations. Brief task progress updates are acceptable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX coordinate in screen pixels (may be negative for secondary displays)
yYesY coordinate in screen pixels (may be negative for secondary displays)

Implementation Reference

  • Handler function for move_mouse tool.
    /** Handle move_mouse tool call. */
    async function handleMoveMouse(
      args: Record<string, unknown>,
    ): Promise<CallToolResult> {
      const parsed = MoveMouseInputSchema.parse(args);
    
      const result = await runInputHelper("move", { x: parsed.x, y: parsed.y });
    
      const response: Record<string, unknown> = {
        moved_to: { x: parsed.x, y: parsed.y },
      };
      if (typeof result.warning === "string") {
        response.warning = result.warning;
      }
    
      return {
        content: [{ type: "text" as const, text: JSON.stringify(response) }],
      };
    }
  • Input schema for move_mouse tool.
    const MoveMouseInputSchema = z.object({
      x: z
        .number()
        .int()
        .describe(
          "X coordinate in screen pixels (may be negative for secondary displays)",
        ),
      y: z
        .number()
        .int()
        .describe(
          "Y coordinate in screen pixels (may be negative for secondary displays)",
        ),
    });
  • Registration of move_mouse tool.
    {
      name: "move_mouse",
      description: `Move the mouse cursor to the specified screen coordinates without clicking. ${SILENT_HINT}`,
      inputSchema: zodToToolInputSchema(MoveMouseInputSchema),
      annotations: {
        readOnlyHint: false,
        destructiveHint: false,
      },
    },
Behavior3/5

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

Annotations already indicate this is not read-only and not destructive, which aligns with the description's implication of a non-destructive action. The description adds behavioral context about not narrating observations and allowing brief progress updates, but does not disclose other traits like performance, side effects, or system dependencies beyond what annotations cover.

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?

The description is front-loaded with the core purpose in the first sentence, followed by two concise behavioral directives. Every sentence adds value without redundancy, making it efficient and well-structured.

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?

Given the tool's low complexity (simple action with two parameters), 100% schema coverage, and no output schema, the description is mostly complete. It covers purpose, behavioral constraints, and usage context, but lacks details on error handling or coordinate system specifics that could enhance completeness.

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?

The input schema has 100% description coverage, fully documenting the x and y parameters. The description does not add any parameter-specific semantics beyond what the schema provides, such as coordinate system details or usage examples, so it meets the baseline of 3.

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?

The description clearly states the specific action ('Move the mouse cursor'), the target ('to the specified screen coordinates'), and what it does not do ('without clicking'). It distinguishes from sibling tools like 'click', 'drag', and 'get_cursor_position' by specifying no clicking occurs.

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?

The description provides clear context on when to use this tool (to move the cursor without clicking) and implicitly distinguishes it from alternatives like 'click' or 'drag'. However, it does not explicitly state when not to use it or name specific alternatives, which prevents a score of 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/antbotlab/mac-use-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server