Skip to main content
Glama
Ruashots
by Ruashots

coolify_delete_database

Delete a database from your Coolify infrastructure. Optionally remove associated volumes and configuration files.

Instructions

Delete a database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesDatabase UUID
delete_volumesNoDelete associated volumes
delete_configurationsNoDelete configuration files
Behavior2/5

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

With no annotations, the description carries the full burden. It only says 'Delete a database' without disclosing any behavioral traits such as irreversibility, effects on associated data, or permission requirements. The optional parameters for volumes and configurations are not mentioned.

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

Conciseness2/5

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

The description is a single sentence, which is under-specified for a delete operation with optional flags. It lacks important details and does not earn its place as a complete description.

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 tool with three parameters and no output schema, the description is inadequate. It fails to explain the effect of the optional parameters or the return behavior, leaving the agent with insufficient information.

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 coverage is 100% as per context signals, so the baseline is 3. The description does not add any extra meaning beyond what the schema provides for the parameters.

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 'Delete a database', clearly identifying the verb and resource. However, it does not distinguish this tool from other delete tools like coolify_delete_service or coolify_delete_application, which are present among siblings.

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?

No guidance is provided on when to use this tool versus alternatives. The description only states the action, leaving the agent without context for selection.

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/Ruashots/coolify-mcp'

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