Skip to main content
Glama

macos_mouse_click

Clicks the mouse at its current macOS position, supporting left, right, middle, double-click, and modifier-held clicks; move the cursor first and grant Accessibility permission.

Instructions

macOS only. Click the mouse at its current position. Covers left/right/middle click and double-click via arguments (button, doubleClick, modifiers), so this one tool handles regular click, right-click, double-click and modifier clicks. Move the cursor first with macos_mouse_move. Requires Accessibility permission.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "macos_mouse_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
buttonNoWhich button to click. Defaults to left.
modifiersNoModifiers held during the click: Shift or Meta/Command to extend a selection, Alt/Option, Control. Example: ["Meta"] is a Cmd+click.
doubleClickNoDeliver a double-click (reported to the OS as a real double-click). Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the important traits: macOS-only platform restriction, that the click happens at the CURRENT position rather than supplied coordinates, and that Accessibility permission is required. It omits what happens on permission failure and whether any result is returned, which are the remaining gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Platform constraint and core action are front-loaded, and the sentences are short. There is mild redundancy between 'Covers left/right/middle click and double-click via arguments' and the following sentence restating the same variants, which could be merged.

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 three-parameter, fully documented, non-destructive-ish input with no output schema, the description covers platform, permission prerequisite, position semantics and the sibling to call first. Only failure/return behavior is unaddressed, a minor gap at this complexity.

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% and each parameter already has an enum or descriptive text, so the schema does the heavy lifting. The description names the three parameters and frames them as click variants, but adds no format or edge-case detail beyond what the schema already states.

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?

States a specific verb and resource ('Click the mouse at its current position') and immediately enumerates the variants covered (left/right/middle, double, modifiers), which lets an agent distinguish it from macos_mouse_drag, macos_mouse_scroll and macos_mouse_move without opening a schema.

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

Usage Guidelines4/5

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

Explicitly routes cursor positioning to macos_mouse_move first, which is the key sequencing decision for this tool. It does not name when-not-to-use cases (e.g., clicking at arbitrary coordinates, which would require a move first), but the practical guidance is clear.

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