Skip to main content
Glama
VetCoders

automator-mcp

by VetCoders

system_automation

Execute system-level automation tasks on macOS, including managing files, controlling displays, capturing screenshots, and toggling system settings through predefined commands.

Instructions

Perform system-level automation tasks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesSystem task to perform
parametersNoTask-specific parameters

Implementation Reference

  • The main handler function for the 'system_automation' tool. It maps tasks to AppleScript commands and executes them using runAppleScript.
    async runSystemAutomation(args) {
      const { task, parameters = {} } = args;
      
      const systemTasks = {
        empty_trash: 'tell application "Finder" to empty trash',
        show_desktop: 'tell application "Finder" to reveal desktop',
        hide_all_apps: 'tell application "System Events" to set visible of every process to false',
        sleep_display: 'do shell script "pmset displaysleepnow"',
        take_screenshot: 'do shell script "screencapture -i ~/Desktop/screenshot.png"',
        start_screensaver: 'tell application "System Events" to start current screen saver',
        toggle_dark_mode: `
          tell application "System Events"
            tell appearance preferences
              set dark mode to not dark mode
            end tell
          end tell
        `,
        get_system_info: `
          set sysInfo to system info
          return (computer name of sysInfo) & " - " & (system version of sysInfo)
        `,
      };
      
      if (systemTasks[task]) {
        return await this.runAppleScript(systemTasks[task]);
      }
      
      throw new Error(`Unknown system task: ${task}`);
    }
  • The tool schema registration, including name, description, and input schema definition for 'system_automation'.
    {
      name: 'system_automation',
      description: 'Perform system-level automation tasks',
      inputSchema: {
        type: 'object',
        properties: {
          task: {
            type: 'string',
            enum: [
              'empty_trash',
              'show_desktop',
              'hide_all_apps',
              'sleep_display',
              'take_screenshot',
              'start_screensaver',
              'toggle_dark_mode',
              'get_system_info',
            ],
            description: 'System task to perform',
          },
          parameters: {
            type: 'object',
            description: 'Task-specific parameters',
          },
        },
        required: ['task'],
      },
    },
  • src/index.js:190-191 (registration)
    Dispatch case in the CallToolRequestSchema handler that routes 'system_automation' calls to the runSystemAutomation method.
    case 'system_automation':
      return await this.runSystemAutomation(args);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'automation tasks' which implies potential system modifications, but fails to disclose critical behavioral traits such as permissions required, side effects (e.g., 'empty_trash' destroys files), or safety considerations, leaving significant gaps for an agent.

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?

The description is a single, efficient sentence that is appropriately sized and front-loaded. It avoids unnecessary words, though it could be more informative; every word earns its place, but the brevity limits helpfulness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of system automation with 2 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on return values, error handling, or behavioral context needed for safe and effective use, failing to compensate for the missing structured data.

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 schema already documents both parameters thoroughly, including an enum for 'task' and a description for 'parameters'. The description adds no additional meaning beyond what the schema provides, such as explaining task-specific behaviors or parameter usage, meeting the baseline for high schema coverage.

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

Purpose3/5

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

The description 'Perform system-level automation tasks' states a general purpose but is vague about what specific resources or actions are involved. It distinguishes from siblings like 'create_workflow' or 'list_actions' by focusing on system-level tasks rather than workflow management or listing, but lacks specificity about the exact verb+resource combination.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'run_applescript' or 'quick_action', there is no indication of context, prerequisites, or exclusions for choosing this automation tool over others, leaving usage decisions ambiguous.

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/VetCoders/automator-mcp'

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