Skip to main content
Glama

mouse_move

Moves the mouse cursor to specified X and Y coordinates. Provides clear error feedback when the endpoint is unsupported, ensuring reliable automation.

Instructions

Move mouse cursor via optional /mouse_move endpoint. Returns clear error when endpoint is unsupported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesTarget X coordinate.
yYesTarget Y coordinate.

Implementation Reference

  • MCP tool registration for 'mouse_move'. Defines the tool name, description, input schema (x,y coordinates as nonnegative ints), and the handler that calls executionService.mouseMove().
    server.registerTool(
      'mouse_move',
      {
        description:
          'Move mouse cursor via optional /mouse_move endpoint. Returns clear error when endpoint is unsupported.',
        inputSchema: {
          x: z.number().int().nonnegative().describe('Target X coordinate.'),
          y: z.number().int().nonnegative().describe('Target Y coordinate.'),
        },
      },
      async ({ x, y }) => {
        logInfo('tool.mouse_move.start', {
          x,
          y,
        });
    
        try {
          const result = await executionService.mouseMove({
            x,
            y,
          });
    
          logInfo('tool.mouse_move.success', {
            x,
            y,
            status: result.status,
          });
    
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(
                  {
                    status: result.status,
                    ok: true,
                    response: result.body,
                  },
                  null,
                  2,
                ),
              },
            ],
          };
        } catch (error) {
          logError('tool.mouse_move.failure', error, {
            x,
            y,
          });
          return toErrorResult(error);
        }
      },
    );
  • Domain service method mouseMove() that delegates to the HotkeylessAhkClient.mouseMove() method.
    public async mouseMove(input: MouseMoveRequest): Promise<EndpointActionResult> {
      return this.client.mouseMove(input);
    }
  • TypeScript interface MouseMoveRequest defining the input shape: x (number) and y (number).
    export interface MouseMoveRequest {
      x: number;
      y: number;
    }
  • Infrastructure client method mouseMove() that sends the payload to the optional 'mouse_move' endpoint via tryOptionalEndpoint().
    public async mouseMove(payload: MouseMoveRequest): Promise<EndpointActionResult> {
      return this.tryOptionalEndpoint(payload, 'mouse_move');
    }
  • Helper method tryOptionalEndpoint() which wraps the payload into a TriggerRequest and calls triggerCommand(), used by mouseMove.
    private async tryOptionalEndpoint(
      payload: unknown,
      endpointName: string,
    ): Promise<EndpointActionResult> {
      const obj: TriggerRequest = {
          command: endpointName,
          params: payload as Record<string, unknown>,
      }
      return this.triggerCommand(obj);
    }
Behavior2/5

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

No annotations provided, so description must disclose behavior. It mentions returning a clear error when unsupported but fails to clarify whether movement is absolute or relative, or any side effects. Minimal disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, but the first sentence partially repeats the tool name. Could be more concise by omitting the endpoint redundancy. Acceptable but not optimal.

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

Completeness2/5

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

No output schema exists, but the description omits key details like coordinate system (absolute vs relative), screen bounds, or error types. Incomplete for confident tool use.

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%, with clear descriptions for x and y. The description adds no additional parameter meaning beyond what the schema provides, so baseline 3 is appropriate.

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 action (Move mouse cursor) and the resource (optional endpoint). It distinguishes from sibling tools like discover_commands and send_keys, which are unrelated to mouse movement.

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?

No guidance on when to use this tool versus alternatives. The description lacks context for when mouse movement is appropriate or how it relates to other commands.

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/tim0-12432/HotkeylessAHK-mcp-skill'

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