macos-control-mcp

Overview Schema Source Related Servers Discussions Admin

click_element

Click a named UI element in an app window. Returns a screenshot by default; disable with return_screenshot=false.

Instructions

Click a named UI element in an app window. Returns a screenshot by default (disable with return_screenshot=false). Use get_ui_elements to discover element names. 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": {
      "app": "<app>",
      "name": "<name>"
    },
    "name": "click_element"
  }
}

Input Schema

Name	Required	Description
`app`	Yes	Application process name
`name`	Yes	Name of the UI element to click
`return_screenshot`	No	Return a screenshot after clicking (default true). Set false for faster/smaller responses.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.13May 29, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description must fully disclose behavior. It notes the screenshot return default and the option to disable it, but does not mention potential side effects (e.g., triggering events) or error conditions.

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, each serving a distinct purpose: purpose, behavior, and usage guidance. No 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?

The description covers purpose, parameter semantics, and usage context. Lacks details on error handling or element discovery, but is sufficient for a simple 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 description coverage is 100%, so baseline is 3. The description adds value by explaining the purpose of each parameter (e.g., 'discover element names' for name) and the default value of return_screenshot, but does not significantly extend beyond schema details.

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 clearly states the verb ('Click') and the resource ('a named UI element in an app window'). This distinguishes it from sibling tools like click_at (coordinates) and click_by_text (text-based).

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?

It advises using get_ui_elements to discover element names and prefers batch_actions for combining actions. This provides context on when to use alternatives, though it lacks explicit statements about when not to use the tool.

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