Skip to main content
Glama

coolify_application_envs

Manage application environment variables in Coolify by listing, creating, updating in bulk, or deleting them to configure application settings.

Instructions

Application environment variables management - list, create, bulk update, and delete environment variables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: list (list environment variables), create (create environment variable), bulk_update (bulk update environment variables), delete (delete environment variable)
uuidYesApplication UUID (required for all actions)
keyNoEnvironment variable key (required for create action)
valueNoEnvironment variable value (required for create action)
env_uuidNoEnvironment variable UUID (required for delete action)
envsNoArray of environment variables (required for bulk_update action)

Implementation Reference

  • The main handler function that implements the logic for the 'coolify_application_envs' tool. It handles actions: list, create, bulk_update, delete by making API calls to manage application environment variables.
    async applicationEnvs(action: string, args: any) {
      if (!args.uuid) throw new Error('Application UUID is required for all environment variable actions');
      
      switch (action) {
        case 'list':
          const response = await this.apiClient.get(`/applications/${args.uuid}/envs`);
          return { content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }] };
        case 'create':
          if (!args.key || !args.value) throw new Error('Key and value are required for create action');
          const createResponse = await this.apiClient.post(`/applications/${args.uuid}/envs`, {
            key: args.key,
            value: args.value,
          });
          return { content: [{ type: 'text', text: JSON.stringify(createResponse.data, null, 2) }] };
        case 'bulk_update':
          if (!args.envs) throw new Error('Environment variables array is required for bulk_update action');
          const bulkResponse = await this.apiClient.patch(`/applications/${args.uuid}/envs/bulk`, {
            envs: args.envs,
          });
          return { content: [{ type: 'text', text: JSON.stringify(bulkResponse.data, null, 2) }] };
        case 'delete':
          if (!args.env_uuid) throw new Error('Environment variable UUID is required for delete action');
          await this.apiClient.delete(`/applications/${args.uuid}/envs/${args.env_uuid}`);
          return { content: [{ type: 'text', text: 'Environment variable deleted successfully' }] };
        default:
          throw new Error(`Unknown application environment variables action: ${action}`);
      }
    }
  • Defines the Tool object including name, description, and inputSchema for the 'coolify_application_envs' tool, used for tool listing and validation.
    {
      name: 'coolify_application_envs',
      description: 'Application environment variables management - list, create, bulk update, and delete environment variables',
      inputSchema: {
        type: 'object',
        properties: {
          action: { 
            type: 'string', 
            enum: ['list', 'create', 'bulk_update', 'delete'],
            description: 'Action to perform: list (list environment variables), create (create environment variable), bulk_update (bulk update environment variables), delete (delete environment variable)'
          },
          uuid: { 
            type: 'string', 
            description: 'Application UUID (required for all actions)' 
          },
          key: { 
            type: 'string', 
            description: 'Environment variable key (required for create action)' 
          },
          value: { 
            type: 'string', 
            description: 'Environment variable value (required for create action)' 
          },
          env_uuid: { 
            type: 'string', 
            description: 'Environment variable UUID (required for delete action)' 
          },
          envs: { 
            type: 'array', 
            description: 'Array of environment variables (required for bulk_update action)',
            items: {
        type: 'object',
        properties: {
                key: { type: 'string' },
                value: { type: 'string' },
              },
              required: ['key', 'value'],
            },
          },
        },
        required: ['action', 'uuid'],
      },
    },
  • src/index.ts:106-107 (registration)
    Switch case in handleToolCall that dispatches calls to the 'coolify_application_envs' tool to the appropriate handler method.
    case 'coolify_application_envs':
      return await this.handlers.applicationEnvs(args.action, args);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it indicates the tool performs CRUD operations, it lacks critical information about permissions needed, whether operations are destructive, rate limits, error handling, or what happens to existing variables during bulk updates. For a multi-action tool with mutation capabilities, this is insufficient.

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 efficiently structured as a single phrase listing the four actions. It's front-loaded with the core purpose and avoids unnecessary elaboration. However, it could be slightly more structured by separating actions with clearer formatting.

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 complex multi-action tool with 6 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain return values, error conditions, or the relationship between actions and parameters. The agent must rely entirely on the schema for operational details, which is insufficient for safe tool invocation.

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%, providing complete parameter documentation. The description adds minimal value beyond the schema by listing the four action types, but doesn't explain parameter interactions, dependencies, or provide usage examples. Baseline 3 is appropriate when 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 'Application environment variables management' with specific verbs (list, create, bulk update, delete) and resource (environment variables). It distinguishes from siblings like coolify_service_envs by specifying 'application' scope, but doesn't explicitly contrast with other environment-related tools.

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 like coolify_service_envs or other application management tools. It lists actions but offers no context about appropriate use cases, prerequisites, or exclusions.

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