Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Create service

coolify_create_service
Destructive

Create a Coolify service from a predefined template by providing the site, project UUID, server UUID, environment name, and service type; optionally deploy it immediately.

Instructions

[UNIFIED] Create a Coolify service from a predefined template. Requires project_uuid, server_uuid, environment, and service type.

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>",
      "type": "<type>"
    },
    "name": "coolify_create_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
siteYes
typeYes
descriptionNo
server_uuidYes
project_uuidYes
instant_deployNo
environment_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered elsewhere; the description adds nothing beyond that. It does not mention instantiating with instant_deploy, what resources get provisioned, or that repeat calls create duplicate services.

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 short sentences, front-loaded with the action and constraint, with no filler. The bracketed "[UNIFIED]" prefix is the only wasted token.

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 an 8-parameter, 5-required, destructive creation tool with no output schema, the description is far too thin. An agent cannot learn from it what 'site' means, what values 'type' accepts, or what happens on deploy.

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% across 8 parameters, so the description must compensate and largely fails. It names project_uuid, server_uuid, environment and type, but silently omits the required 'site' parameter, plus name, description and instant_deploy; it also calls it 'environment' while the field is environment_name.

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 service) and narrows the source to a predefined template, which distinguishes it from the sibling create_application_* tools. The leading "[UNIFIED]" tag carries no meaning for an agent.

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?

Implies the when-to-use condition (pick this when deploying a templated one-click service rather than a Dockerfile/compose/image app), but never states it explicitly and gives no exclusions or prerequisites beyond a bare list of required inputs.

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