computer-use-mac-mcp

double_click

Clicks twice at the specified screen coordinates to open files, launch apps, or activate interface elements, using pixel positions from screenshots for precise targeting.

Instructions

Double-click the left mouse button at the specified 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": "double_click"
  }
}

Input Schema

Name	Required	Description	Default
`x`	Yes	Horizontal position (pixel coordinate in the screenshot coordinate space)
`y`	Yes	Vertical position (pixel coordinate in the screenshot coordinate space)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It states the core action but does not disclose potential behavioral details such as whether the cursor is moved to the coordinates first or the timing of the two clicks. This is adequate for a simple operation but leaves some context unspecified.

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?

One sentence with no wasted words; the verb is front-loaded and the object and location are clear. Every word earns its place.

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?

For a tool with only two fully documented parameters and no output schema, the description is concise and sufficient for correct invocation. It could mention the mouse movement behavior, but nothing critical is missing for an agent to call the tool correctly.

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 x and y already described as pixel coordinates in screenshot space. The description adds no parameter semantics beyond what the schema provides, so a baseline of 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 uses a precise verb 'Double-click' and specifies the resource 'left mouse button at specified coordinates', clearly distinguishing it from sibling tools like left_click and right_click.

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

Usage Guidelines3/5

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

No explicit when-to-use or alternative guidance is given; usage is only implied by the action itself. The agent must infer that double_click is for double-clicking rather than single-clicking, but the description does not discuss exclusions or alternatives.

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

Deploy Server