Skip to main content
Glama

coolify_project_environments

Manage project environments by listing, creating, retrieving details, or deleting them within Coolify infrastructure projects.

Instructions

Project environment management - list, create, get, and delete project environments

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: list (list all environments in project), create (create new environment), get (get environment details), delete (delete environment)
project_uuidYesProject UUID (required for all actions)
environment_name_or_uuidNoEnvironment name or UUID (required for get and delete actions)
nameNoEnvironment name (required for create action)

Implementation Reference

  • The handler function that implements the execution logic for the coolify_project_environments tool, dispatching to API endpoints based on the action (list, create, get, delete).
    async projectEnvironments(action: string, args: any) {
      if (!args.project_uuid) throw new Error('Project UUID is required for all project environment actions');
      
      switch (action) {
        case 'list':
          const response = await this.apiClient.get(`/projects/${args.project_uuid}/environments`);
          return { content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }] };
        case 'create':
          if (!args.name) throw new Error('Environment name is required for create action');
          const createResponse = await this.apiClient.post(`/projects/${args.project_uuid}/environments`, {
            name: args.name,
          });
          return { content: [{ type: 'text', text: JSON.stringify(createResponse.data, null, 2) }] };
        case 'get':
          if (!args.environment_name_or_uuid) throw new Error('Environment name or UUID is required for get action');
          const getResponse = await this.apiClient.get(`/projects/${args.project_uuid}/${args.environment_name_or_uuid}`);
          return { content: [{ type: 'text', text: JSON.stringify(getResponse.data, null, 2) }] };
        case 'delete':
          if (!args.environment_name_or_uuid) throw new Error('Environment name or UUID is required for delete action');
          const deleteResponse = await this.apiClient.delete(`/projects/${args.project_uuid}/environments/${args.environment_name_or_uuid}`);
          return { content: [{ type: 'text', text: JSON.stringify(deleteResponse.data, null, 2) }] };
        default:
          throw new Error(`Unknown project environments action: ${action}`);
      }
    }
  • The tool definition including name, description, and input schema for validation.
    {
      name: 'coolify_project_environments',
      description: 'Project environment management - list, create, get, and delete project environments',
      inputSchema: {
        type: 'object',
        properties: {
          action: { 
            type: 'string', 
            enum: ['list', 'create', 'get', 'delete'],
            description: 'Action to perform: list (list all environments in project), create (create new environment), get (get environment details), delete (delete environment)'
          },
          project_uuid: { 
            type: 'string', 
            description: 'Project UUID (required for all actions)' 
          },
          environment_name_or_uuid: { 
            type: 'string', 
            description: 'Environment name or UUID (required for get and delete actions)' 
          },
          name: { 
            type: 'string', 
            description: 'Environment name (required for create action)' 
          },
        },
        required: ['action', 'project_uuid'],
      },
    },
  • src/index.ts:98-99 (registration)
    The switch case in handleToolCall that registers and routes calls to the projectEnvironments handler.
    case 'coolify_project_environments':
      return await this.handlers.projectEnvironments(args.action, args);
  • src/index.ts:60-63 (registration)
    Registers the listTools handler which returns all tools including coolify_project_environments via getTools().
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: getTools(),
      };
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. While it mentions the four operations (list, create, get, delete), it doesn't explain important behavioral aspects like: what permissions are needed for each action, whether deletions are permanent or reversible, if there are rate limits, what the response format looks like, or any side effects of these operations.

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 appropriately concise - a single sentence that efficiently communicates the core functionality. It's front-loaded with the main purpose. However, it could be slightly more structured by separating the different action types more clearly.

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 tool with 4 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain the relationships between parameters (e.g., which parameters are needed for which actions beyond what the schema indicates), doesn't describe return values or error conditions, and doesn't provide context about how this fits within the broader Coolify ecosystem relative to sibling tools.

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, so the schema already documents all four parameters thoroughly. The description doesn't add any meaningful parameter semantics beyond what's in the schema - it just lists the four action types without explaining parameter dependencies or usage patterns. The baseline of 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 as 'Project environment management - list, create, get, and delete project environments', which is a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling tools like 'coolify_application_envs' or 'coolify_service_envs', which might handle similar environment 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. There are multiple sibling tools with 'envs' in their names (coolify_application_envs, coolify_service_envs), but the description doesn't explain whether this tool is for project-level environments specifically or how it differs from those other environment tools.

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