Skip to main content
Glama

send_mouse_move

Move the mouse cursor to precise coordinates (x, y) using Scenic MCP for AI-driven automation and testing of Scenic Elixir applications.

Instructions

Move mouse cursor to specific coordinates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX coordinate
yYesY coordinate

Implementation Reference

  • The handler function that checks connection, constructs the mouse move command with x and y coordinates, sends it to the Elixir/Scenic backend via conn.sendToElixir, parses response, and returns success or error message.
    async function handleSendMouseMove(args: any) {
      try {
        const isRunning = await conn.checkTCPServer();
        if (!isRunning) {
          return {
            content: [
              {
                type: 'text',
                text: 'Cannot send mouse move: No Scenic application connected.\n\nStart your Scenic application first.',
              },
            ],
            isError: false,
          };
        }
    
        const { x, y } = args;
    
        const command = {
          action: 'send_mouse_move',
          x,
          y,
        };
    
        const response = await conn.sendToElixir(command);
        const data = JSON.parse(response);
    
        if (data.error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error moving mouse: ${data.error}`,
              },
            ],
            isError: true,
          };
        }
    
        return {
          content: [
            {
              type: 'text',
              text: `Mouse moved to (${x}, ${y})`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error moving mouse: ${error instanceof Error ? error.message : 'Unknown error'}`,
            },
          ],
          isError: true,
        };
      }
  • The tool schema defining the name, description, and input schema requiring x and y numeric coordinates.
    {
      name: 'send_mouse_move',
      description: 'CURSOR MOVEMENT: Move the mouse cursor to specific coordinates. Useful for hover effects, precise positioning before clicking, and testing mouse-over interactions.',
      inputSchema: {
        type: 'object',
        properties: {
          x: {
            type: 'number',
            description: 'X coordinate',
          },
          y: {
            type: 'number',
            description: 'Y coordinate',
          },
        },
        required: ['x', 'y'],
      },
    },
  • src/tools.ts:196-197 (registration)
    The switch case in the tool handler router that dispatches calls to 'send_mouse_move' to the handleSendMouseMove function.
    case 'send_mouse_move':
      return await handleSendMouseMove(args);
  • src/tools.ts:72-72 (registration)
    The tool name registration within the getToolDefinitions array.
    name: 'send_mouse_move',
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but doesn't disclose behavioral traits like whether this requires specific permissions, if it's immediate or queued, what happens if coordinates are out of bounds, if it affects other UI elements, or any side effects. For a system interaction tool with zero annotation coverage, this is a significant 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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core action and appropriately sized for a simple tool with two parameters.

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?

Given this is a system interaction tool (mouse movement) with no annotations, no output schema, and siblings that suggest a UI automation context (Scenic), the description is incomplete. It doesn't address prerequisites, coordinate system, behavioral constraints, or what success/failure looks like, leaving significant gaps for an AI agent.

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 description coverage is 100%, with both parameters (x and y) clearly documented in the schema as coordinates. The description adds no additional meaning beyond what the schema provides (e.g., coordinate system origin, units, or valid ranges). Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the verb ('Move') and resource ('mouse cursor') with the specific action ('to specific coordinates'). It distinguishes from siblings like send_mouse_click (clicking vs moving) and send_keys (keyboard input). However, it doesn't explicitly differentiate from other potential mouse movement tools that might exist in other contexts.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing to connect to Scenic first using connect_scenic), when mouse movement is appropriate versus other input methods, or any constraints on coordinate ranges or system state.

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

Related 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/scenic-contrib/scenic_mcp_experimental'

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