Skip to main content
Glama
0xtlt

coolify-mcp

by 0xtlt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

coolify_create_database

[WRITE] Create a new Coolify database

Instructions

[WRITE] Create a new Coolify database

Input Schema

NameRequiredDescriptionDefault
nameNoDatabase name
typeYesDatabase engine type
imageNoDocker image (e.g. postgres:16-alpine)
is_publicNoMake database publicly accessible
descriptionNoDatabase description
limits_cpusNoCPU limit (e.g. 0.5, 2)
public_portNoPublic port number
server_uuidYesUUID of the server to deploy on
type_configNoType-specific config. Postgres: postgres_user, postgres_password, postgres_db. MySQL/MariaDB: mysql_root_password, mysql_database, mysql_user, mysql_password. MongoDB: mongo_initdb_root_username, mongo_initdb_root_password. Redis: redis_password. ClickHouse: clickhouse_admin_user, clickhouse_admin_password. SQLite (Coolify v4.4+, no is_public/public_port): sqlite_databases (comma-separated file names)
project_uuidYesUUID of the project
custom_fieldsNoAdditional fields not listed above (advanced)
limits_memoryNoMemory limit (e.g. 512m, 1g)
instant_deployNoDeploy immediately after creation
environment_nameYesEnvironment name (e.g. 'production')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.3.0
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "postgresql",
-  "mysql",
-  "mariadb",
-  "mongodb",
-  "redis",
-  "dragonfly",
-  "keydb",
-  "clickhouse"
-]New value: +[
+  "postgresql",
+  "mysql",
+  "mariadb",
+  "mongodb",
+  "redis",
+  "dragonfly",
+  "keydb",
+  "clickhouse",
+  "sqlite"
+]
    • changedInput schema / properties / type_config / description
      Previous value: -"Type-specific config. Postgres: postgres_user, postgres_password, postgres_db. MySQL/MariaDB: mysql_root_password, mysql_database, mysql_user, mysql_password. MongoDB: mongo_initdb_root_username, mongo_initdb_root_password. Redis: redis_password. ClickHouse: clickhouse_admin_user, clickhouse_admin_password"New value: +"Type-specific config. Postgres: postgres_user, postgres_password, postgres_db. MySQL/MariaDB: mysql_root_password, mysql_database, mysql_user, mysql_password. MongoDB: mongo_initdb_root_username, mongo_initdb_root_password. Redis: redis_password. ClickHouse: clickhouse_admin_user, clickhouse_admin_password. SQLite (Coolify v4.4+, no is_public/public_port): sqlite_databases (comma-separated file names)"
  2. First observedv4.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. The '[WRITE]' marker confirms mutation, but the description does not mention required permissions, side effects, whether deployment happens immediately, or what happens when dependencies are missing. For a create operation with 14 parameters and no annotations, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded phrase with no waste, but it is under-sized for a complex mutation with 14 parameters and nested configuration. It is concise without being appropriately complete.

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 a 14-parameter creation tool with nested type_config, no annotations, and no output schema, the description is too thin. It does not explain required relationships, engine-specific configuration expectations, or post-creation behavior, leaving critical context to the schema alone.

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 all 14 parameters, including the enum type and nested type_config, are documented in the schema itself. The description adds no parameter meaning beyond that, which meets the baseline for high-coverage schemas but does not exceed it.

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 clear verb ('Create') and resource ('Coolify database'), and the '[WRITE]' tag signals mutation. Its specificity distinguishes it from siblings such as coolify_create_application and coolify_create_service, though it adds no scope detail beyond the noun.

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?

There is no guidance on when to use this tool versus alternatives like coolify_import_database, nor any prerequisites such as an existing server, project, or environment. The agent is left to infer usage entirely from the tool name.

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