Skip to main content
Glama
VetCoders

automator-mcp

by VetCoders

create_workflow

Create new Automator workflows to automate macOS tasks like file organization, email sending, and system operations using AppleScript or JXA actions.

Instructions

Create a new Automator workflow file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the workflow
typeYesType of Automator document
actionsNoArray of action configurations

Implementation Reference

  • The handler function that implements the 'create_workflow' tool logic. It generates an AppleScript to create a new Automator workflow with the given name and type, executes it, and returns a success message.
    async createWorkflow(args) {
      // Simplified workflow creation - in real implementation would use Automator's plist format
      const workflowScript = `
        tell application "Automator"
          make new workflow
          set name of result to "${args.name}"
          save result
        end tell
      `;
      
      await this.runAppleScript(workflowScript);
      
      return {
        content: [
          {
            type: 'text',
            text: `Created ${args.type} workflow: ${args.name}`,
          },
        ],
      };
    }
  • src/index.js:65-94 (registration)
    Registration of the 'create_workflow' tool in the listTools response, including name, description, and input schema definition.
    {
      name: 'create_workflow',
      description: 'Create a new Automator workflow file',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Name of the workflow',
          },
          type: {
            type: 'string',
            enum: ['workflow', 'application', 'service', 'quick-action'],
            description: 'Type of Automator document',
          },
          actions: {
            type: 'array',
            description: 'Array of action configurations',
            items: {
              type: 'object',
              properties: {
                action: { type: 'string' },
                parameters: { type: 'object' },
              },
            },
          },
        },
        required: ['name', 'type'],
      },
    },
  • Dispatch handler case that routes 'create_workflow' tool calls to the createWorkflow method.
    case 'create_workflow':
      return await this.createWorkflow(args);

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the creation action without mentioning side effects (e.g., overwriting existing files), required permissions, error conditions, or return behavior. This is a significant gap for a mutation tool.

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 minimal (one sentence) with no extraneous information. It is concise, but it prioritizes brevity over completeness, omitting important usage context that could be added without significant length.

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 tool's complexity (creation with 3 parameters, no output schema), the description only covers the basic purpose. It lacks information about prerequisites, output behavior, error handling, and integration with sibling tools, making it insufficient for an agent to use the tool correctly without additional assumptions.

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 all parameters have baseline explanations. The tool description adds no additional meaning beyond what the schema already provides, resulting in a baseline score of 3.

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 states the verb 'Create' and resource 'Automator workflow file', making the purpose evident. However, it does not differentiate itself from sibling tools like 'quick_action' or 'run_applescript', which could confuse an AI agent selecting the appropriate tool.

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. The description lacks context for preferred scenarios, prerequisites, or exclusions, leaving the agent without direction for tool selection.

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