Skip to main content
Glama

coolify_database_types

Create PostgreSQL, MySQL, MongoDB, or Redis databases with type-specific parameters for infrastructure management in Coolify environments.

Instructions

Specific database type creation - create PostgreSQL, MySQL, MongoDB, and Redis databases with type-specific parameters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: create (create database of specific type)
typeYesDatabase type (required for create action)
nameYesDatabase name (required for create action)
server_uuidYesServer UUID (required for create action)
project_uuidYesProject UUID (required for create action)
environment_nameYesEnvironment name (required for create action)
postgresql_userNoPostgreSQL user (optional for postgresql type)
postgresql_passwordNoPostgreSQL password (optional for postgresql type)
postgresql_dbNoPostgreSQL database name (optional for postgresql type)
mysql_userNoMySQL user (optional for mysql type)
mysql_passwordNoMySQL password (optional for mysql type)
mysql_databaseNoMySQL database name (optional for mysql type)
mysql_root_passwordNoMySQL root password (optional for mysql type)
mongodb_root_usernameNoMongoDB root username (optional for mongodb type)
mongodb_root_passwordNoMongoDB root password (optional for mongodb type)
mongodb_databaseNoMongoDB database name (optional for mongodb type)
mongodb_usernameNoMongoDB username (optional for mongodb type)
mongodb_passwordNoMongoDB password (optional for mongodb type)
redis_passwordNoRedis password (optional for redis type)

Implementation Reference

  • Core handler function for 'coolify_database_types' tool. Validates action as 'create' and required 'type', then POSTs to API endpoint `/databases/{type}` with arguments and returns formatted response.
    async databaseTypes(action: string, args: any) {
      if (action !== 'create') throw new Error('Only create action is supported for database types');
      if (!args.type) throw new Error('Database type is required for create action');
      
      const endpoint = `/databases/${args.type}`;
      const response = await this.apiClient.post(endpoint, args);
      return { content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }] };
    }
  • src/tools.ts:429-481 (registration)
    Tool registration in getTools() array, defining name, description, and detailed inputSchema for 'coolify_database_types' with type-specific parameters for PostgreSQL, MySQL, MongoDB, Redis.
    {
      name: 'coolify_database_types',
      description: 'Specific database type creation - create PostgreSQL, MySQL, MongoDB, and Redis databases with type-specific parameters',
      inputSchema: {
        type: 'object',
        properties: {
          action: { 
            type: 'string', 
            enum: ['create'],
            description: 'Action to perform: create (create database of specific type)'
          },
          type: { 
            type: 'string', 
            enum: ['postgresql', 'mysql', 'mongodb', 'redis'],
            description: 'Database type (required for create action)' 
          },
          name: { 
            type: 'string', 
            description: 'Database name (required for create action)' 
          },
          server_uuid: { 
            type: 'string', 
            description: 'Server UUID (required for create action)' 
          },
          project_uuid: { 
            type: 'string', 
            description: 'Project UUID (required for create action)' 
          },
          environment_name: { 
            type: 'string', 
            description: 'Environment name (required for create action)' 
          },
          // PostgreSQL specific parameters
          postgresql_user: { type: 'string', description: 'PostgreSQL user (optional for postgresql type)' },
          postgresql_password: { type: 'string', description: 'PostgreSQL password (optional for postgresql type)' },
          postgresql_db: { type: 'string', description: 'PostgreSQL database name (optional for postgresql type)' },
          // MySQL specific parameters
          mysql_user: { type: 'string', description: 'MySQL user (optional for mysql type)' },
          mysql_password: { type: 'string', description: 'MySQL password (optional for mysql type)' },
          mysql_database: { type: 'string', description: 'MySQL database name (optional for mysql type)' },
          mysql_root_password: { type: 'string', description: 'MySQL root password (optional for mysql type)' },
          // MongoDB specific parameters
          mongodb_root_username: { type: 'string', description: 'MongoDB root username (optional for mongodb type)' },
          mongodb_root_password: { type: 'string', description: 'MongoDB root password (optional for mongodb type)' },
          mongodb_database: { type: 'string', description: 'MongoDB database name (optional for mongodb type)' },
          mongodb_username: { type: 'string', description: 'MongoDB username (optional for mongodb type)' },
          mongodb_password: { type: 'string', description: 'MongoDB password (optional for mongodb type)' },
          // Redis specific parameters
          redis_password: { type: 'string', description: 'Redis password (optional for redis type)' },
        },
        required: ['action', 'type', 'name', 'server_uuid', 'project_uuid', 'environment_name'],
      },
    },
  • Switch case in handleToolCall that routes 'coolify_database_types' calls to the handlers.databaseTypes method.
    case 'coolify_database_types':
      return await this.handlers.databaseTypes(args.action, args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a creation tool but doesn't mention permission requirements, whether it's idempotent, what happens on failure, or typical response format. For a tool with 19 parameters and no output schema, this leaves significant behavioral gaps for the agent.

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 a single, efficient sentence that front-loads the core purpose. It wastes no words but could potentially benefit from slightly more context given the tool's complexity. Every word earns its place, though it might be too concise for a tool with 19 parameters.

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 complex creation tool with 19 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what happens after creation, error conditions, or how this tool relates to the broader database management context provided by sibling tools. The agent would struggle to use this effectively without additional context.

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 the schema already documents all 19 parameters thoroughly. The description adds minimal value beyond the schema by mentioning 'type-specific parameters' and listing the four database types, but doesn't provide additional context about parameter relationships or usage patterns. This meets the baseline for high schema coverage.

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 clearly states the tool's purpose: 'Specific database type creation - create PostgreSQL, MySQL, MongoDB, and Redis databases with type-specific parameters.' It specifies the verb ('create') and resources (four database types), but doesn't explicitly differentiate from sibling tools like 'coolify_databases' or 'coolify_database_lifecycle' which might handle other database operations.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, dependencies, or compare it to sibling tools like 'coolify_databases' (which might list databases) or 'coolify_database_lifecycle' (which might manage existing databases). The agent must infer usage from the name and description alone.

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/HowieDuhzit/CoolifyMCP'

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