Skip to main content
Glama
Sign In
computer-use-mac-mcp

computer-use-mac-mcp

by somethingforheheda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

middle_click

Perform a middle mouse button click at specified pixel coordinates to trigger actions like opening links in new tabs or auto-scrolling during macOS desktop automation.

Instructions

Click the middle 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": "middle_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesHorizontal position (pixel coordinate in the screenshot coordinate space)
yYesVertical position (pixel coordinate in the screenshot coordinate space)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action but does not clarify whether the cursor is moved, how press/release events are handled, or whether system-specific middle-click side effects apply.

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, direct sentence with no redundancy. Every word contributes to the meaning.

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?

For a simple two-parameter primitive, the description plus the schema is minimally sufficient to invoke the tool. However, the absence of any behavioral or usage context leaves it only adequate, not fully informative.

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 describes both parameters fully with 100% coverage, including the screenshot coordinate space. The description adds no additional parameter semantics, which is acceptable but provides no extra value.

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 states a specific verb ('Click'), a specific resource ('middle mouse button'), and a coordinate target, making it clearly distinct from sibling tools such as left_click, right_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 Guidelines2/5

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

There is no guidance on when to choose middle_click over alternatives, nor any context about middle-click-specific behaviors such as autoscroll or paste in some environments. Usage is only implied by the tool name and sibling list.

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

Deploy Server

Other Tools