Skip to main content
Glama

apple_system

Manage macOS system settings and actions: sleep, restart, lock screen, toggle Wi-Fi/Bluetooth, dark mode, Do Not Disturb, run shortcuts, control audio, and access preferences. Confirm protected actions for execution.

Instructions

System controls: sleep, restart, shutdown, lock, dark mode, DND, caffeinate, wifi, bluetooth, shortcuts, prefs, audio, screen saver, AirDrop, login items, Time Machine, audio devices. Actions: sleep, sleep_display, restart, shutdown, logout, lock, dark_mode, dnd_on, dnd_off, caffeinate, decaffeinate, wifi_status, wifi_on, wifi_off, wifi_network, bluetooth_on, bluetooth_off, run_shortcut, list_shortcuts, open_prefs, display_settings, sound_settings, network_settings, airdrop, screen_saver, login_items, eject_all_disks, time_machine, audio_output, audio_input.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName of the Shortcut to run
paneNoPane name: wifi, bluetooth, sound, display, keyboard, trackpad, battery, security, notifications, general
actionYessleep: Put the Mac to sleep; sleep_display: Turn off the display (sleep display only); restart: Restart the Mac; shutdown: Shut down the Mac; logout: Log out the current user; lock: Lock the screen; dark_mode: Toggle dark mode on/off; dnd_on: Enable Do Not Disturb; dnd_off: Disable Do Not Disturb; caffeinate: Prevent Mac from sleeping for N minutes (default 60); decaffeinate: Stop caffeinate (allow sleep again); wifi_status: Get Wi-Fi power status; wifi_on: Turn Wi-Fi on; wifi_off: Turn Wi-Fi off; wifi_network: Get the current Wi-Fi network name; bluetooth_on: Turn Bluetooth on; bluetooth_off: Turn Bluetooth off; run_shortcut: Run a macOS Shortcut by name; list_shortcuts: List all available macOS Shortcuts; open_prefs: Open System Preferences (optionally a specific pane); display_settings: Open Display preferences (Night Shift, resolution, etc.); sound_settings: Open Sound preferences (output/input devices, volume); network_settings: Open Network preferences; airdrop: Open AirDrop window; screen_saver: Start the screen saver; login_items: List login items (apps that start at login); eject_all_disks: Force-unmount all external disks; time_machine: Get Time Machine backup status; audio_output: Get the current default audio output device; audio_input: Get the current default audio input device
confirmNoSet to true to confirm a protected/destructive action. Without this, protected actions return a preview instead of executing.
minutesNoMinutes to stay awake (default 60)
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 disclosing behavioral traits. It fails to mention that actions like restart, shutdown, and logout are destructive or that protected actions require the confirm parameter. While the schema covers this, the description itself provides no safety or side-effect information.

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

Conciseness3/5

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

The description is a long, flat list that is somewhat redundant (categories overlap with actions) but is front-loaded with 'System controls' and covers all actions. It is adequately sized for the large action set but could be more structured and concise.

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?

The tool is highly complex with 30 actions, and the schema provides detailed action semantics. However, the description lacks output expectations (e.g., what time_machine or audio_output returns) and usage context, making it minimally complete for an agent to safely invoke all actions.

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 the baseline is 3. The description adds no extra parameter meaning beyond listing action names; the schema's per-parameter descriptions already define semantics, so the description provides no additional value here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as 'System controls' and enumerates a comprehensive list of categories and specific actions (sleep, restart, wifi_on, etc.), making it evident that this tool manages system-level settings. It distinguishes from sibling tools by its broad scope, though it lacks an explicit verb phrase like 'controls'.

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?

No guidance is provided on when to use this tool versus alternatives such as apple_brightness or apple_volume. The description simply lists available actions without any context for selection, exclusions, or examples of appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lacausecrypto/apple-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server