computer-use-mac-mcp

right_click

Right-click at the specified screen coordinates to open context menus or trigger secondary actions during desktop automation.

Instructions

Click the right 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": "right_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.6/5.0

Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure, but it only states the action. It does not reveal whether the cursor is moved first, whether a context menu is expected, or what side effects the click may have.

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 that front-loads the action and coordinates. There is no filler or redundant information.

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 simple two-parameter click tool, the description plus schema fully specify how to call it: action, button, coordinates, and coordinate space. Minor behavioral details like cursor movement are missing, but the core invocation is clear.

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 schema already documents both x and y with 100% coverage, including the screenshot coordinate space. The description adds no parameter-level detail beyond this, so the baseline score of 3 applies.

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 specific verb ('Click') and resource ('right mouse button') at specified coordinates, making the tool's purpose unmistakable. It clearly differentiates from sibling tools like left_click, middle_click, and double_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?

Usage is implied by the right-button semantics, but the description gives no explicit guidance on when to prefer this over left_click, double_click, or other mouse tools. It also does not mention typical use cases such as context menus or preconditions.

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

Deploy Server