Skip to main content
Glama

coolify_service_lifecycle

Manage service states in Coolify infrastructure by starting, stopping, or restarting services using their UUID.

Instructions

Service lifecycle management - start, stop, and restart services

Input Schema

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

Implementation Reference

  • The handler function that implements the core logic for the coolify_service_lifecycle tool. It takes action (start/stop/restart) and service UUID, then calls the appropriate Coolify API endpoint and returns the response.
    async serviceLifecycle(action: string, uuid: string) {
      if (!uuid) throw new Error('Service UUID is required for all lifecycle actions');
      
      switch (action) {
        case 'start':
          const startResponse = await this.apiClient.post(`/services/${uuid}/start`);
          return { content: [{ type: 'text', text: JSON.stringify(startResponse.data, null, 2) }] };
        case 'stop':
          const stopResponse = await this.apiClient.post(`/services/${uuid}/stop`);
          return { content: [{ type: 'text', text: JSON.stringify(stopResponse.data, null, 2) }] };
        case 'restart':
          const restartResponse = await this.apiClient.post(`/services/${uuid}/restart`);
          return { content: [{ type: 'text', text: JSON.stringify(restartResponse.data, null, 2) }] };
        default:
          throw new Error(`Unknown service lifecycle action: ${action}`);
      }
    }
  • The tool definition including name, description, and input schema validation for coolify_service_lifecycle.
    {
      name: 'coolify_service_lifecycle',
      description: 'Service lifecycle management - start, stop, and restart services',
      inputSchema: {
        type: 'object',
        properties: {
          action: { 
            type: 'string', 
            enum: ['start', 'stop', 'restart'],
            description: 'Action to perform: start (start service), stop (stop service), restart (restart service)'
          },
          uuid: { 
            type: 'string', 
            description: 'Service UUID (required for all actions)' 
          },
        },
        required: ['action', 'uuid'],
      },
    },
  • src/index.ts:130-131 (registration)
    The switch case in the main tool dispatcher that registers and routes calls to the serviceLifecycle handler for this tool.
    case 'coolify_service_lifecycle':
      return await this.handlers.serviceLifecycle(args.action, args.uuid);
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. It states the actions (start, stop, restart) but doesn't cover critical aspects like required permissions, side effects (e.g., downtime for stop/restart), error handling, or response format. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 purpose ('Service lifecycle management') and lists the specific actions. Every word earns its place with zero waste, making it easy to parse quickly.

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 (managing service states, which implies mutations) and lack of annotations or output schema, the description is incomplete. It doesn't address behavioral traits like safety, permissions, or response details, leaving the agent with insufficient context to use it effectively beyond basic parameter input.

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?

The input schema has 100% description coverage, with clear documentation for both parameters (action with enum values and uuid as required). The description adds no additional parameter semantics beyond what's in the schema, such as explaining UUID format or action nuances. Baseline 3 is appropriate since 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 as 'Service lifecycle management - start, stop, and restart services', which specifies the verb (manage lifecycle) and resource (services) with concrete actions. However, it doesn't differentiate from sibling tools like 'coolify_application_lifecycle' or 'coolify_database_lifecycle', which likely manage similar lifecycle operations for different resource types.

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, distinguish it from sibling tools (e.g., 'coolify_application_lifecycle'), or specify contexts like which services are eligible. Usage is implied by the action names but lacks explicit when/when-not instructions.

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