Skip to main content
Glama

create_dockerfile_application

Set up a new application from a Dockerfile. Provide the base64-encoded Dockerfile content along with project, environment, and server information.

Instructions

Create a new application from a Dockerfile

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_uuidYesProject UUID
environment_nameYesEnvironment name
environment_uuidNoEnvironment UUID (optional)
server_uuidYesServer UUID
destination_uuidNoDestination UUID (optional if server has single destination)
dockerfileYesDockerfile content (base64 encoded)
ports_exposesYesPorts to expose (e.g., "3000,8080")
nameNoApplication name (optional, auto-generated if not provided)
descriptionNoApplication description
instant_deployNoDeploy immediately after creation

Implementation Reference

  • Handler case for 'create_dockerfile_application' tool. Validates required params (project_uuid, environment_name, server_uuid, dockerfile, ports_exposes) and POSTs to /applications/dockerfile endpoint.
    case 'create_dockerfile_application':
      requireParam(args, 'project_uuid');
      requireParam(args, 'environment_name');
      requireParam(args, 'server_uuid');
      requireParam(args, 'dockerfile');
      requireParam(args, 'ports_exposes');
      return client.post('/applications/dockerfile', args);
  • Schema definition for create_dockerfile_application. Defines input properties (project_uuid, environment_name, environment_uuid, server_uuid, destination_uuid, dockerfile, ports_exposes, name, description, instant_deploy) with required fields: project_uuid, environment_name, server_uuid, dockerfile, ports_exposes.
    {
      name: 'create_dockerfile_application',
      description: 'Create a new application from a Dockerfile',
      inputSchema: {
        type: 'object',
        properties: {
          project_uuid: { type: 'string', description: 'Project UUID' },
          environment_name: { type: 'string', description: 'Environment name' },
          environment_uuid: { type: 'string', description: 'Environment UUID (optional)' },
          server_uuid: { type: 'string', description: 'Server UUID' },
          destination_uuid: { type: 'string', description: 'Destination UUID (optional if server has single destination)' },
          dockerfile: { type: 'string', description: 'Dockerfile content (base64 encoded)' },
          ports_exposes: { type: 'string', description: 'Ports to expose (e.g., "3000,8080")' },
          name: { type: 'string', description: 'Application name (optional, auto-generated if not provided)' },
          description: { type: 'string', description: 'Application description' },
          instant_deploy: { type: 'boolean', description: 'Deploy immediately after creation', default: false }
        },
        required: ['project_uuid', 'environment_name', 'server_uuid', 'dockerfile', 'ports_exposes']
      }
  • The handleTool function is exported from handlers.ts and registered via ListToolsRequestSchema/CallToolRequestSchema in src/index.ts (lines 36-67). The tool name 'create_dockerfile_application' is matched in a switch statement.
    import { CoolifyClient } from '../client.js';
    import { ErrorCode, McpError } from '@modelcontextprotocol/sdk/types.js';
    import { isConfirmRequired, isDangerousOperation, getDangerWarning } from './definitions.js';
Behavior2/5

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

No annotations provided, so description must bear full burden. Only states it creates an application, but does not disclose side effects, permissions required, or what happens on failure. Lacks behavioral details beyond the basic action.

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?

Extremely concise single sentence, front-loaded with key information. No wasted words, but slightly underspecified given the complexity.

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 10 parameters, no output schema, and no annotations, the description is insufficient. Does not explain return value, deployment behavior, or error conditions. Agent lacks full context to use tool correctly.

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%, so baseline is 3. The tool description adds no additional meaning beyond what the schema already provides for each parameter. No extra context or clarification.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

Description clearly states verb 'Create', resource 'application', and source 'Dockerfile'. It distinguishes from siblings like 'create_dockercompose_application' and 'create_dockerimage_application' by specifically mentioning Dockerfile.

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?

No guidance on when to use this tool versus alternatives (e.g., create_dockercompose_application, create_dockerimage_application). No exclusions or context provided; the description is too brief to help with decision-making.

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/kof70/coolify-mcp-server'

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