Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Create application public

coolify_create_application_public
Destructive

Deploy a public Git repository as a Coolify application by providing the project, server, environment, branch, build pack, and exposed ports.

Instructions

[UNIFIED] Create a Coolify application from a public Git repository. Requires project_uuid, server_uuid, environment, git_repository, git_branch, build_pack, and ports_exposes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "project_uuid": "<project_uuid>",
      "server_uuid": "<server_uuid>",
      "environment_name": "<environment_name>",
      "git_repository": "<git_repository>",
      "git_branch": "<git_branch>",
      "build_pack": "<build_pack>",
      "ports_exposes": "<ports_exposes>"
    },
    "name": "coolify_create_application_public"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
siteYes
domainsNo
build_packYes
git_branchYes
descriptionNo
server_uuidYes
project_uuidYes
ports_exposesYes
git_repositoryYes
instant_deployNo
environment_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the safety profile is covered. The description adds nothing beyond that — it does not warn that this provisions a real resource, does not explain what instant_deploy does, and does not mention whether a deploy is triggered.

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?

Two sentences, front-loaded, with no filler. The required-parameter sentence partially duplicates the schema's 'required' list, which slightly undercuts efficiency.

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 destructive, non-idempotent creation tool with twelve undocumented parameters and no output schema, the description is far too thin — an agent learns nothing about parameter formats, default behavior, or what happens after creation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, yet it only restates the names of required parameters without meaning. Twelve parameters including build_pack, ports_exposes, domains, instant_deploy, and name receive no format, default, or value guidance.

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?

States a specific verb and resource: 'Create a Coolify application from a public Git repository.' The 'public Git repository' qualifier implicitly separates it from siblings like coolify_create_application_private_github_app or coolify_create_application_dockerfile, but no sibling is named explicitly.

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 gives no when-to-use guidance: it does not say when to pick this over the dockerfile, docker_image, compose, or private_github_app variants, nor does it mention any prerequisites or consequences of creating the application.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools