Skip to main content
Glama

create_workflow

Create new workflows in Automatisch to automate business processes and integrate applications using this MCP server tool.

Instructions

Create a new workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesWorkflow name
descriptionNoWorkflow description
activeNoWhether workflow should be active

Implementation Reference

  • src/handlers.ts:42-63 (registration)
    Tool registration entry in the ListTools handler, defining the name, description, and input schema for 'create_workflow'.
    {
      name: "create_workflow",
      description: "Create a new workflow",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "Workflow name"
          },
          description: {
            type: "string",
            description: "Workflow description"
          },
          active: {
            type: "boolean",
            description: "Whether workflow should be active",
            default: false
          }
        },
        required: ["name"]
      }
  • Input schema defining the parameters for the create_workflow tool (name required, optional description and active flag).
    inputSchema: {
      type: "object",
      properties: {
        name: {
          type: "string",
          description: "Workflow name"
        },
        description: {
          type: "string",
          description: "Workflow description"
        },
        active: {
          type: "boolean",
          description: "Whether workflow should be active",
          default: false
        }
      },
      required: ["name"]
    }
  • MCP tool handler logic that delegates execution to main.api.createWorkflow and returns the result as a text content block.
    case "create_workflow":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(await main.api.createWorkflow(args), null, 2)
          }
        ]
      };
  • API helper method stub for createWorkflow, intended to contain the core logic for creating a workflow (delegated to by the tool handler).
    createWorkflow: async function(data: any) {
      // ... copy createWorkflow logic from index.ts ...
    },
  • Initializes the 'api' object on the main server instance using apiHelpers, providing access to createWorkflow for handlers.
    public api = apiHelpers(this);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create a new workflow' implies a write operation, but it doesn't disclose permissions needed, whether creation is idempotent, error conditions, or what happens upon success (e.g., returns a workflow ID). For a mutation tool with zero annotation coverage, this is a significant gap.

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 sentence with zero waste, making it appropriately concise. However, it's under-specified rather than efficiently informative—it could benefit from more detail without losing conciseness. It's front-loaded but lacks depth.

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 creating a workflow (a mutation with 3 parameters), no annotations, and no output schema, the description is incomplete. It doesn't explain what a workflow is, what happens after creation, or how to handle errors. For a tool with siblings like 'delete_workflow' and 'update_workflow', more context is needed to ensure proper use.

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%, with all parameters documented in the schema (name, description, active). The description adds no parameter-specific information beyond what the schema provides, such as constraints on the name or implications of the active flag. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states the basic action ('Create a new workflow') which is clear but vague. It doesn't specify what a workflow entails in this context or distinguish it from sibling tools like 'create_connection' or 'update_workflow'. The purpose is understandable but lacks specificity about the resource being created.

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. It doesn't mention prerequisites, when to choose this over 'update_workflow', or how it relates to sibling tools like 'list_workflows' or 'test_workflow'. Users must infer usage from the tool name alone.

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/milisp/automatisch-mcp-server'

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