Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Get database backups

coolify_get_database_backups
Read-only

Retrieve backup configuration and history for a Coolify database to verify schedules, retention settings, and recent backup runs.

Instructions

[UNIFIED] Get backup configuration and history for a Coolify database.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3/5.0
Behavior3/5

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

readOnlyHint=true already declares this is a safe, non-mutating read, so the annotation carries the safety profile. The description adds modest value by disclosing the response content ('configuration and history'), but says nothing about pagination, history depth, permissions, or what happens for a database with no backups.

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?

A single front-loaded sentence with no wasted wording. The only inefficiency is the '[UNIFIED]' tag, which conveys nothing actionable to an agent.

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

Completeness3/5

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

The tool is simple, read-only, has no output schema, and the annotations cover its safety profile, so a brief description is defensible. However, with two required parameters at 0% schema coverage, the definition is not quite complete enough for reliable invocation without external knowledge of Coolify.

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?

Schema description coverage is 0%, so the description must compensate — and it does not. 'uuid' is only loosely implied by 'for a Coolify database', and the required 'site' parameter (likely the Coolify instance/URL) is never mentioned at all, leaving an agent to guess its meaning.

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?

States a specific verb ('Get') and resource ('backup configuration and history for a Coolify database'), which distinguishes it from the mutating sibling coolify_create_database_backup and from coolify_get_database itself. The '[UNIFIED]' prefix is opaque noise but does not obscure the core purpose.

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 on when to use this versus alternatives, and no prerequisites or context are given. An agent must infer from the sibling names alone that this is the read counterpart to coolify_create_database_backup.

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