Skip to main content
Glama
0xtlt

coolify-mcp

by 0xtlt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

coolify_set_database_storage_backup

[WRITE] Create or replace a backup schedule for a database persistent volume/directory

Instructions

[WRITE] Create or replace a backup schedule for a database persistent volume/directory

Input Schema

NameRequiredDescriptionDefault
uuidYesUUID of the database
enabledNoWhether the schedule is enabled (default true)
save_s3NoAlso upload backups to S3
timeoutNoBackup timeout in seconds
frequencyYesCron frequency for the backup (e.g. '0 2 * * *')
storage_uuidYesUUID of the persistent volume or directory storage
s3_storage_uuidNoS3 storage UUID when save_s3 is true
retention_days_s3No
stop_during_backupNoStop the resource during backup
retention_amount_s3No
disable_local_backupNoDisable local backup retention
retention_days_locallyNo
retention_amount_locallyNo
retention_max_storage_s3No
retention_max_storage_locallyNo
missing_backup_notification_daysNoAlert after this many days without an execution; 0 disables alerts (Coolify v4.4.1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.3.0
    • addedInput schema / properties / missing_backup_notification_days
      Added value: +{
+  "description": "Alert after this many days without an execution; 0 disables alerts (Coolify v4.4.1)",
+  "maximum": 365,
+  "minimum": 0,
+  "type": "integer"
+}
    • removedInput schema / properties / s3_storage_uuid / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / s3_storage_uuid / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Changed2 schema fields changedv4.1.0
    • changedInput schema / properties / timeout / maximum
      Previous value: -9007199254740991New value: +36000
    • changedInput schema / properties / timeout / minimum
      Previous value: --9007199254740991New value: +60
  3. First observedv4.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It discloses that this is a write operation and uses 'create or replace,' implying that an existing schedule is overwritten, but it does not explain permission requirements, whether unspecified parameters reset, or what happens to existing backup data—critical gaps for a 16-parameter mutation tool.

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 front-loaded sentence with no wasted words, though its extreme brevity leaves much unexplained for a complex 16-parameter tool.

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 the tool's complexity—16 parameters, no annotations, no output schema—the one-sentence description is insufficient. It fails to explain how the replace behavior works, what defaults apply, or how retention parameters interact, leaving an agent without enough context to invoke it safely.

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?

The description adds no meaning beyond the schema, which covers only 63% of parameters. Several parameters (e.g., retention_days_s3, retention_amount_s3, retention_max_storage_locally) lack description text, and the tool's description does nothing to compensate for these gaps.

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 a specific verb ('Create or replace') and resource ('a backup schedule for a database persistent volume/directory'). It distinguishes itself from siblings like coolify_run_database_storage_backup and coolify_delete_database_storage_backup by focusing on schedule creation/replacement, 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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The '[WRITE]' tag implies mutability but offers no further usage context.

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