Skip to main content
Glama

Create Application — Dockerfile

coolify_create_application_dockerfile

Create an application from a Dockerfile without requiring a Git repository. Provide the Dockerfile content and deploy instantly.

Instructions

Create an application from a Dockerfile without Git. You can deploy a simple Dockerfile by providing its content directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoApplication display name
revealNoReveal redacted secret values in the response (default false; the call is audited)
domainsNoFQDN for the app
instanceYesREQUIRED — which Coolify instance to mutate: 'prod' (Hetzner VPS) or 'dev' (local OrbStack VM). No default: state the target explicitly so a write never lands on prod by accident.
dockerfileYesFull Dockerfile content as a string
descriptionNoApplication description
server_uuidYesServer UUID
project_uuidYesUUID of the target project
ports_exposesNoPorts to expose8080
destination_uuidYesDestination UUID
environment_nameNoEnvironment nameproduction
Behavior3/5

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

Annotations indicate this is a write operation (readOnlyHint=false) and not idempotent (idempotentHint=false). The description adds minimal behavioral context, only noting that deployment occurs. No contradiction with annotations.

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?

Extremely concise with two sentences. The core purpose is front-loaded, and every word is meaningful with no redundancy.

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?

No output schema and no description of the return value or side effects. With 11 parameters, a bit more detail on what happens after creation (e.g., deployment status) would be beneficial.

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 coverage is 100% and parameter descriptions are already clear in the schema. The description does not add extra meaning or usage tips beyond what the schema provides.

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?

The description clearly states the verb 'Create', the resource 'application', and the method 'from a Dockerfile without Git', distinguishing it from sibling tools that use Docker Compose, images, or Git-based approaches.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for Dockerfile-only deployments but does not explicitly state when to use or avoid this tool, nor does it mention alternatives among the many sibling creation 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/AlobarQuest/infraops-mcp-server'

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