Skip to main content
Glama
Sign In
cPanel MCP Server

cPanel MCP Server

by 0xHayd3n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_database_backup

Create a backup of a MySQL database to protect against data loss. Specify the database name to generate a backup copy.

Instructions

Create a backup of a specific MySQL 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": {
      "database": "<database>"
    },
    "name": "create_database_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
databaseYesDatabase name to backup

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention side effects, storage location, retention, or whether existing backups are overwritten. For a mutation-like operation, this is a significant gap.

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 fluff. It is appropriately sized for a simple tool, though it could benefit from a brief usage note without becoming verbose.

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?

For a simple one-parameter tool with no output schema, the description is minimally adequate. However, given the sibling tools for different backup types, a brief note on how this differs from create_full_backup or restore_database_backup would improve completeness. The core purpose is conveyed, but the broader backup context is missing.

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% for the single parameter, so the schema already documents the parameter clearly. The description adds minimal extra meaning beyond restating that the database is a MySQL database, which is already implied. Baseline 3 is appropriate.

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 action (create a backup) and the target resource (specific MySQL database), distinguishing it from other backup tools like create_full_backup or create_homedir_backup. However, it does not explicitly name sibling alternatives, so it slightly misses the top score.

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 other backup tools (e.g., create_full_backup, restore_database_backup). The description only states what it does, not the appropriate context or exclusions.

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