coolify-mcp

Delete database

deleteDatabase

Destructive

Delete a database by UUID and clean up its configurations, volumes, connected networks, and Docker resources. Set flags to false to retain any of these.

Instructions

Delete a database by UUID. By default Coolify also deletes configurations, volumes, and connected networks and runs docker cleanup; pass the flags as false to keep them.

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": {
      "uuid": "<uuid>"
    },
    "name": "deleteDatabase"
  }
}

Input Schema

Name	Required	Description	Default
`uuid`	Yes
`delete_volumes`	No
`docker_cleanup`	No
`delete_configurations`	No
`delete_connected_networks`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.5Aug 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description details exactly what gets deleted by default (configurations, volumes, connected networks, docker cleanup) and how to opt out. This provides valuable operational transparency for an agent.

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

Conciseness5/5

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

Two sentences, front-loaded with the primary action. No redundant information; every phrase adds value, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the destructive nature and 5 parameters, the description adequately explains default behavior and customization. It lacks return value details, but with no output schema and a simple delete operation, the provided context is sufficient.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates by explaining the UUID as the identifier and describing the boolean flags as controlling deletion of specific resources. It groups the params meaningfully, though it doesn't name each individually.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Delete a database by UUID') with a specific resource and identifier method. It distinguishes from sibling tools like updateDatabase or getDatabase by focusing on deletion and the unique UUID parameter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context on default destructive behavior and how to preserve resources by setting flags to false. While it doesn't explicitly exclude scenarios or name alternatives, the usage context is well-defined for a deletion tool.

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

Deploy Server