Skip to main content
Glama
Sign In
macos-control-mcp

macos-control-mcp

by PeterHdd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

click_at

Click at specified screen coordinates to interact with UI elements on macOS. Optionally returns a screenshot; set return_screenshot=false for faster execution.

Instructions

Click at x,y screen coordinates. Returns a screenshot by default (disable with return_screenshot=false). Use screenshot + screen_ocr to find coordinates first. Prefer batch_actions when combining with other actions.

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": "click_at"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX coordinate
yYesY coordinate
return_screenshotNoReturn a screenshot after clicking (default true). Set false for faster/smaller responses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.13

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description carries burden. Discloses default behavior (returns screenshot) and how to disable it. However, does not specify coordinate system (screen vs window) or potential side effects, but sufficient for most use cases.

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?

Three sentences, front-loaded with action. No redundant or irrelevant content. Efficiently conveys key 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?

Covers return behavior (screenshot), hints at tool integration (ocr, batch), and explains disable option. Missing coordinate system detail but otherwise complete for a click tool with no output schema.

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%, baseline 3. Description adds no new parameter meaning beyond schema descriptions (which already state defaults and effects). Adequate but not enhanced.

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?

Specifies verb 'click' and resource 'x,y screen coordinates'. Distinguishes from siblings like click_by_text (text-based) and click_element (element-based). Clear and unambiguous.

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

Usage Guidelines5/5

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

Explicitly suggests using screenshot and screen_ocr to find coordinates first. Recommends batch_actions when combining with other actions, providing clear when-to-use and when-not-to-use guidance.

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