Skip to main content
Glama

create_connection

Establish a new app connection in Automatisch by providing app identifier, connection name, and required credentials to enable workflow automation.

Instructions

Create a new app connection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appKeyYesApp identifier (e.g., 'slack', 'github')
nameYesConnection name
credentialsYesApp-specific credentials and configuration

Implementation Reference

  • MCP tool handler for 'create_connection': invokes the API helper method and formats the response as JSON text.
    case "create_connection":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(await main.api.createConnection(args), null, 2)
          }
        ]
      };
  • Input schema definition for the 'create_connection' tool, specifying required parameters: appKey, name, credentials.
    {
      name: "create_connection",
      description: "Create a new app connection",
      inputSchema: {
        type: "object",
        properties: {
          appKey: {
            type: "string",
            description: "App identifier (e.g., 'slack', 'github')"
          },
          name: {
            type: "string",
            description: "Connection name"
          },
          credentials: {
            type: "object",
            description: "App-specific credentials and configuration"
          }
        },
        required: ["appKey", "name", "credentials"]
      }
    },
  • API helper method 'createConnection' that is called by the tool handler (currently a placeholder for the core implementation logic).
    createConnection: async function(data: any) {
      // ... copy createConnection logic from index.ts ...
    },
  • src/handlers.ts:32-279 (registration)
    Registration of the CallToolRequestHandler which dispatches to specific tool cases, including 'create_connection'.
              type: "object",
              properties: {
                workflowId: {
                  type: "string",
                  description: "Workflow ID to retrieve"
                }
              },
              required: ["workflowId"]
            }
          },
          {
            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"]
            }
          },
          {
            name: "update_workflow",
            description: "Update an existing workflow",
            inputSchema: {
              type: "object",
              properties: {
                workflowId: {
                  type: "string",
                  description: "Workflow ID to update"
                },
                name: {
                  type: "string",
                  description: "New workflow name"
                },
                description: {
                  type: "string",
                  description: "New workflow description"
                },
                active: {
                  type: "boolean",
                  description: "Workflow active status"
                }
              },
              required: ["workflowId"]
            }
          },
          {
            name: "delete_workflow",
            description: "Delete a workflow",
            inputSchema: {
              type: "object",
              properties: {
                workflowId: {
                  type: "string",
                  description: "Workflow ID to delete"
                }
              },
              required: ["workflowId"]
            }
          },
          {
            name: "list_connections",
            description: "List all app connections",
            inputSchema: {
              type: "object",
              properties: {
                appKey: {
                  type: "string",
                  description: "Filter by specific app"
                }
              }
            }
          },
          {
            name: "create_connection",
            description: "Create a new app connection",
            inputSchema: {
              type: "object",
              properties: {
                appKey: {
                  type: "string",
                  description: "App identifier (e.g., 'slack', 'github')"
                },
                name: {
                  type: "string",
                  description: "Connection name"
                },
                credentials: {
                  type: "object",
                  description: "App-specific credentials and configuration"
                }
              },
              required: ["appKey", "name", "credentials"]
            }
          },
          {
            name: "list_executions",
            description: "List workflow executions",
            inputSchema: {
              type: "object",
              properties: {
                workflowId: {
                  type: "string",
                  description: "Filter by workflow ID"
                },
                status: {
                  type: "string",
                  enum: ["success", "failure", "running"],
                  description: "Filter by execution status"
                },
                limit: {
                  type: "number",
                  description: "Limit number of results"
                }
              }
            }
          },
          {
            name: "get_available_apps",
            description: "Get list of available apps and their capabilities",
            inputSchema: {
              type: "object",
              properties: {
                category: {
                  type: "string",
                  description: "Filter by app category"
                }
              }
            }
          },
          {
            name: "test_workflow",
            description: "Test a workflow with sample data",
            inputSchema: {
              type: "object",
              properties: {
                workflowId: {
                  type: "string",
                  description: "Workflow ID to test"
                },
                testData: {
                  type: "object",
                  description: "Sample data for testing"
                }
              },
              required: ["workflowId"]
            }
          }
        ]
      };
    });
    
    // List available resources
    server.setRequestHandler(ListResourcesRequestSchema, async () => {
      return {
        resources: [
          {
            uri: "automatisch://workflows",
            mimeType: "application/json",
            name: "Workflows Overview",
            description: "Overview of all workflows and their status"
          },
          {
            uri: "automatisch://connections",
            mimeType: "application/json",
            name: "App Connections",
            description: "List of configured app connections"
          },
          {
            uri: "automatisch://apps",
            mimeType: "application/json",
            name: "Available Apps",
            description: "Catalog of available apps and integrations"
          },
          {
            uri: "automatisch://executions/recent",
            mimeType: "application/json",
            name: "Recent Executions",
            description: "Recent workflow executions and their results"
          }
        ]
      };
    });
    
    // Handle resource reading
    server.setRequestHandler(ReadResourceRequestSchema, async (request: any) => {
      const { uri } = request.params;
      switch (uri) {
        case "automatisch://workflows":
          return {
            contents: [
              {
                uri,
                mimeType: "application/json",
                text: JSON.stringify(await main.api.getWorkflowsOverview(), null, 2)
              }
            ]
          };
        case "automatisch://connections":
          return {
            contents: [
              {
                uri,
                mimeType: "application/json",
                text: JSON.stringify(await main.api.getConnectionsOverview(), null, 2)
              }
            ]
          };
        case "automatisch://apps":
          return {
            contents: [
              {
                uri,
                mimeType: "application/json",
                text: JSON.stringify(await main.api.getAvailableApps(), null, 2)
              }
            ]
          };
        case "automatisch://executions/recent":
          return {
            contents: [
              {
                uri,
                mimeType: "application/json",
                text: JSON.stringify(await main.api.getRecentExecutions(), null, 2)
              }
            ]
          };
        default:
          throw new McpError(ErrorCode.InvalidRequest, `Unknown resource: ${uri}`);
      }
    });
    
    // Handle tool calls
    server.setRequestHandler(CallToolRequestSchema, async (request: any) => {
  • Initializes the 'api' object on the main server instance with API helpers, providing 'createConnection' method.
    public api = apiHelpers(this);
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this requires specific permissions, whether it's idempotent, what happens on failure, or typical response format, which are critical for a creation tool.

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?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action, making it easy to parse quickly, though this conciseness comes at the cost of detail.

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?

For a creation tool with no annotations and no output schema, the description is incomplete. It lacks information on success/failure behavior, return values, error handling, or how it fits with siblings like 'get_available_apps', leaving significant gaps for agent usage.

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 parameters are well-documented in the schema. The description adds no extra meaning beyond implying 'app connection' relates to 'appKey', but this is already clear from the schema, meeting the baseline for high 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 states the action ('create') and resource ('app connection'), which is clear but minimal. It doesn't differentiate from siblings like 'create_workflow' or 'list_connections', leaving ambiguity about what an 'app connection' specifically is versus other connection types or workflows.

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. For example, it doesn't mention prerequisites like needing 'get_available_apps' first, or contrast with 'list_connections' for viewing existing ones, leaving the agent to infer usage context.

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