Skip to main content
Glama

coolify_server_management

Validate server connections, list domains, and manage resources for infrastructure oversight using server UUID and action parameters.

Instructions

Server operations and resources - validate server connection, list domains, and list resources

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: validate (validate server connection), domains (list server domains), resources (list server resources)
uuidYesServer UUID (required for all actions)

Implementation Reference

  • The serverManagement method in the CoolifyHandlers class executes the coolify_server_management tool. It handles the three supported actions (validate, domains, resources) by making API calls to the Coolify server endpoints using the provided server UUID and returns the JSON-stringified response.
    async serverManagement(action: string, uuid: string) {
      if (!uuid) throw new Error('Server UUID is required for all server management actions');
      
      switch (action) {
        case 'validate':
          const validateResponse = await this.apiClient.get(`/servers/${uuid}/validate`);
          return { content: [{ type: 'text', text: JSON.stringify(validateResponse.data, null, 2) }] };
        case 'domains':
          const domainsResponse = await this.apiClient.get(`/servers/${uuid}/domains`);
          return { content: [{ type: 'text', text: JSON.stringify(domainsResponse.data, null, 2) }] };
        case 'resources':
          const resourcesResponse = await this.apiClient.get(`/servers/${uuid}/resources`);
          return { content: [{ type: 'text', text: JSON.stringify(resourcesResponse.data, null, 2) }] };
        default:
          throw new Error(`Unknown server management action: ${action}`);
      }
    }
  • Defines the Tool object for coolify_server_management in the getTools() array, including name, description, and inputSchema specifying the action enum and required server uuid.
    {
      name: 'coolify_server_management',
      description: 'Server operations and resources - validate server connection, list domains, and list resources',
      inputSchema: {
        type: 'object',
        properties: {
          action: { 
            type: 'string', 
            enum: ['validate', 'domains', 'resources'],
            description: 'Action to perform: validate (validate server connection), domains (list server domains), resources (list server resources)'
          },
          uuid: { 
            type: 'string', 
            description: 'Server UUID (required for all actions)' 
          },
        },
        required: ['action', 'uuid'],
      },
    },
  • src/index.ts:124-125 (registration)
    Registers the coolify_server_management tool in the MCP server's handleToolCall switch statement by dispatching to the handlers.serverManagement method.
    case 'coolify_server_management':
      return await this.handlers.serverManagement(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 mentions operations like 'validate server connection' and 'list domains/resources', but doesn't describe what these actions entail—e.g., whether validation is a lightweight ping or a full audit, if listing returns all data or is paginated, or if there are rate limits or authentication requirements. For a tool with multiple actions and no annotations, this leaves significant gaps in understanding behavior.

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 concise and front-loaded, stating the tool's purpose in a single sentence with three bullet-like actions. There's no wasted text, and it efficiently communicates the scope. However, it could be slightly more structured by explicitly separating the actions or adding brief context, but it remains appropriately sized for its content.

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 (multiple actions, no output schema, no annotations), the description is incomplete. It lacks details on what each action returns, error conditions, or behavioral traits like whether operations are read-only or have side effects. Without annotations or output schema, the description should compensate more by explaining expected outputs or usage constraints, which it doesn't do adequately.

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 minimal value beyond the schema by naming the actions (validate, domains, resources), but doesn't provide additional context like what 'validate' checks or what 'resources' includes. With high schema coverage, the baseline is 3, as the description doesn't significantly enhance parameter understanding.

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 performs server operations and resources with three specific actions: validate server connection, list domains, and list resources. It provides a verb+resource combination that distinguishes it from siblings like coolify_servers (likely listing servers) or coolify_system (broader system operations). However, it doesn't explicitly differentiate from all siblings, such as coolify_logs which might also involve server resources.

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, such as needing a valid server UUID from another tool like coolify_servers, or clarify when to choose this over siblings like coolify_servers for server-level operations versus coolify_applications for application-level tasks. Usage is implied through action names but not explicitly stated.

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