Skip to main content
Glama

coolify_application_lifecycle

Manage application states by starting, stopping, or restarting applications using their unique identifiers within the Coolify infrastructure platform.

Instructions

Application lifecycle management - start, stop, and restart applications

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: start (start application), stop (stop application), restart (restart application)
uuidYesApplication UUID (required for all actions)

Implementation Reference

  • Executes the application lifecycle actions (start, stop, restart) by calling the Coolify API endpoints.
    async applicationLifecycle(action: string, uuid: string) {
      if (!uuid) throw new Error('Application UUID is required for all lifecycle actions');
      
      switch (action) {
        case 'start':
          const startResponse = await this.apiClient.post(`/applications/${uuid}/start`);
          return { content: [{ type: 'text', text: JSON.stringify(startResponse.data, null, 2) }] };
        case 'stop':
          const stopResponse = await this.apiClient.post(`/applications/${uuid}/stop`);
          return { content: [{ type: 'text', text: JSON.stringify(stopResponse.data, null, 2) }] };
        case 'restart':
          const restartResponse = await this.apiClient.post(`/applications/${uuid}/restart`);
          return { content: [{ type: 'text', text: JSON.stringify(restartResponse.data, null, 2) }] };
        default:
          throw new Error(`Unknown application lifecycle action: ${action}`);
      }
    }
  • Defines the tool schema including input parameters: action (enum: start, stop, restart) and uuid.
    {
      name: 'coolify_application_lifecycle',
      description: 'Application lifecycle management - start, stop, and restart applications',
      inputSchema: {
        type: 'object',
        properties: {
          action: { 
            type: 'string', 
            enum: ['start', 'stop', 'restart'],
            description: 'Action to perform: start (start application), stop (stop application), restart (restart application)'
          },
          uuid: { 
            type: 'string', 
            description: 'Application UUID (required for all actions)' 
          },
        },
        required: ['action', 'uuid'],
      },
    },
  • src/index.ts:104-105 (registration)
    Registers the tool handler dispatch in the main tool call switch statement.
    case 'coolify_application_lifecycle':
      return await this.handlers.applicationLifecycle(args.action, args.uuid);
Behavior2/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 behavioral disclosure. It states the actions but doesn't describe effects (e.g., whether stop is graceful, if restart preserves state), permissions required, error conditions, or rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 that front-loads the core functionality ('Application lifecycle management') and lists the specific actions. There is zero waste or redundancy, making it highly concise and well-structured for quick understanding.

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 (mutation operations with no annotations and no output schema), the description is incomplete. It lacks information on behavioral traits, error handling, return values, and usage context. While the schema covers parameters well, the overall description fails to provide sufficient context for safe and effective 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 clear descriptions for both parameters (action with enum values and UUID as required). The description adds no additional parameter semantics beyond what the schema provides, such as UUID format or action-specific behaviors. 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.

Purpose4/5

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

The description clearly states the tool's purpose with specific verbs ('start, stop, and restart applications') and identifies the resource ('applications'). It distinguishes from siblings like 'coolify_application_deployments' or 'coolify_service_lifecycle' by focusing on lifecycle operations rather than deployments or service management. However, it doesn't explicitly differentiate from 'coolify_service_lifecycle' which might have overlapping functionality.

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 (e.g., application must exist), exclusions (e.g., cannot be used for databases), or compare to siblings like 'coolify_service_lifecycle' or 'coolify_database_lifecycle'. Usage is implied by the action names but lacks explicit 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/HowieDuhzit/CoolifyMCP'

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