Skip to main content
Glama
senseisven

MCP Remote macOS Control Server

by senseisven

remote_macos_mouse_double_click

Perform a mouse double-click at specified coordinates on a remote macOS machine. This tool enables remote control by executing double-click actions with automatic coordinate scaling for accurate positioning.

Instructions

Perform a mouse double-click at specified coordinates on a remote MacOs machine, with automatic coordinate scaling. Uses environment variables for connection details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX coordinate for mouse position (in source dimensions)
yYesY coordinate for mouse position (in source dimensions)
source_widthNoWidth of the reference screen for coordinate scaling
source_heightNoHeight of the reference screen for coordinate scaling
buttonNoMouse button (1=left, 2=middle, 3=right)

Implementation Reference

  • The core handler function that scales input coordinates based on source and target screen dimensions, connects to the remote MacOS via VNC, performs the double-click using vnc.send_mouse_click with double_click=True, and returns a status message.
    def handle_remote_macos_mouse_double_click(arguments: dict[str, Any]) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:
        """Perform a mouse double-click action on a remote MacOs machine."""
        # Use environment variables
        host = MACOS_HOST
        port = MACOS_PORT
        password = MACOS_PASSWORD
        username = MACOS_USERNAME
        encryption = VNC_ENCRYPTION
    
        # Get required parameters from arguments
        x = arguments.get("x")
        y = arguments.get("y")
        source_width = int(arguments.get("source_width", 1366))
        source_height = int(arguments.get("source_height", 768))
        button = int(arguments.get("button", 1))
    
        if x is None or y is None:
            raise ValueError("x and y coordinates are required")
    
        # Ensure source dimensions are positive
        if source_width <= 0 or source_height <= 0:
            raise ValueError("Source dimensions must be positive values")
    
        # Initialize VNC client
        vnc = VNCClient(host=host, port=port, password=password, username=username, encryption=encryption)
    
        # Connect to remote MacOs machine
        success, error_message = vnc.connect()
        if not success:
            error_msg = f"Failed to connect to remote MacOs machine at {host}:{port}. {error_message}"
            return [types.TextContent(type="text", text=error_msg)]
    
        try:
            # Get target screen dimensions
            target_width = vnc.width
            target_height = vnc.height
    
            # Scale coordinates
            scaled_x = int((x / source_width) * target_width)
            scaled_y = int((y / source_height) * target_height)
    
            # Ensure coordinates are within the screen bounds
            scaled_x = max(0, min(scaled_x, target_width - 1))
            scaled_y = max(0, min(scaled_y, target_height - 1))
    
            # Double click
            result = vnc.send_mouse_click(scaled_x, scaled_y, button, True)
    
            # Prepare the response with useful details
            scale_factors = {
                "x": target_width / source_width,
                "y": target_height / source_height
            }
    
            return [types.TextContent(
                type="text",
                text=f"""Mouse double-click (button {button}) from source ({x}, {y}) to target ({scaled_x}, {scaled_y}) {'succeeded' if result else 'failed'}
    Source dimensions: {source_width}x{source_height}
    Target dimensions: {target_width}x{target_height}
    Scale factors: {scale_factors['x']:.4f}x, {scale_factors['y']:.4f}y"""
            )]
        finally:
            # Close VNC connection
            vnc.close()
  • Input schema definition for the tool, specifying required x,y coordinates and optional source dimensions and button.
    types.Tool(
        name="remote_macos_mouse_double_click",
        description="Perform a mouse double-click at specified coordinates on a remote MacOs machine, with automatic coordinate scaling. Uses environment variables for connection details.",
        inputSchema={
            "type": "object",
            "properties": {
                "x": {"type": "integer", "description": "X coordinate for mouse position (in source dimensions)"},
                "y": {"type": "integer", "description": "Y coordinate for mouse position (in source dimensions)"},
                "source_width": {"type": "integer", "description": "Width of the reference screen for coordinate scaling", "default": 1366},
                "source_height": {"type": "integer", "description": "Height of the reference screen for coordinate scaling", "default": 768},
                "button": {"type": "integer", "description": "Mouse button (1=left, 2=middle, 3=right)", "default": 1}
            },
            "required": ["x", "y"]
        },
    ),
  • Tool dispatch logic in the MCP server's call_tool handler that routes requests with this name to the specific handler function.
    elif name == "remote_macos_mouse_double_click":
        return handle_remote_macos_mouse_double_click(arguments)
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'automatic coordinate scaling' and environment variable usage, but lacks details on error handling, latency, permissions required, or what happens if the remote machine is unavailable. For a remote control tool with zero annotation coverage, this is insufficient.

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 two sentences, front-loaded with the core action, and every word earns its place—no redundancy or fluff. It efficiently conveys purpose and key constraints.

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?

Given 5 parameters with full schema coverage but no annotations or output schema, the description is adequate for basic understanding but lacks depth for a remote control tool. It covers the 'what' but not the 'how' or edge cases, making it minimally viable but with clear gaps in behavioral context.

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%, so the schema fully documents all parameters. The description adds value by explaining 'automatic coordinate scaling' and referencing environment variables, but doesn't provide additional semantic context beyond what's in the schema descriptions. Baseline 3 is appropriate as 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 action ('Perform a mouse double-click'), target ('on a remote MacOs machine'), and key behavior ('with automatic coordinate scaling'). It distinguishes from sibling tools like 'remote_macos_mouse_click' by specifying double-click functionality, though it doesn't explicitly contrast with all siblings.

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 mentions 'Uses environment variables for connection details,' which implies prerequisites but doesn't provide explicit guidance on when to use this tool versus alternatives like 'remote_macos_mouse_click' or 'remote_macos_mouse_drag_n_drop.' No context on exclusions or best practices is given.

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/senseisven/mcp_macos'

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