Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Create server

coolify_create_server
Destructive

Register a new server in Coolify with SSH access details, including name, IP, port, user, and private key UUID.

Instructions

[UNIFIED] Register a new server in Coolify. Requires name, IP, port, user, and a private key UUID for SSH access.

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>",
      "name": "<name>",
      "ip": "<ip>",
      "private_key_uuid": "<private_key_uuid>"
    },
    "name": "coolify_create_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYes
nameYes
portNo
siteYes
userNoroot
proxy_typeNotraefik
descriptionNo
is_build_serverNo
instant_validateNo
private_key_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is supplied structurally. The description adds useful context that SSH access and a private key UUID are needed, but it does not explain validation behavior, side effects, or what makes the operation destructive.

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 short and front-loaded: purpose first, prerequisites second. The unexplained "[UNIFIED]" tag adds noise, but otherwise the two sentences are efficient.

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 create tool with ten parameters, no output schema, and 0% schema description coverage, this is materially incomplete. It omits a required parameter and half the optional configuration surface, leaving the agent dependent on undocumented schema fields.

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 must carry parameter meaning. It names only five of ten parameters and omits the required site parameter entirely; it also mischaracterizes optional port and user parameters as required, while saying nothing about proxy_type, is_build_server, instant_validate, or description.

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 states a specific verb and resource: "Register a new server in Coolify." That is enough to distinguish this tool from get/update/delete server siblings, though it does not explicitly name those alternatives.

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?

It mentions SSH access and a private key UUID as prerequisites, but gives no guidance on when to use this versus coolify_update_server or coolify_validate_server. The required-parameter guidance is also unreliable because it lists port and user as required even though the schema marks them optional with defaults.

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