Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-remove

Destructive

Deletes a MySQL database from Dokploy by its ID, removing the instance and freeing associated deployment resources.

Instructions

POST /mysql.remove

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": {
      "mysqlId": "<mysqlId>"
    },
    "name": "mysql-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
mysqlIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows this is a destructive, externally-visible operation. The description adds nothing beyond that: no statement of what is deleted, whether it is reversible, required permissions, or whether dependent resources (users, databases, ports) are affected.

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?

It is short, but only because it is under-specified rather than economical. A bare route string does not front-load any actionable information.

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

Completeness1/5

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

For a destructive removal tool with no output schema and an undocumented required identifier, the definition is completely inadequate. An agent cannot determine what will be destroyed, what preconditions exist, or how to confirm success.

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

Parameters1/5

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

Schema description coverage is 0% and the single parameter mysqlId is undocumented. The description does not explain whether mysqlId is an instance identifier, name, or UUID, so it fails to compensate for the schema gap.

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

Purpose2/5

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

The description is only "POST /mysql.remove", which restates the tool name and HTTP route rather than describing what the tool does. An agent can infer deletion of a MySQL resource from the name and destructiveHint, but the description itself contributes no verb+resource statement.

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

Usage Guidelines1/5

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

There is no when-to-use or when-not-to-use guidance, and no pointer to related operations (e.g., mysql-stop vs removal, or whether a backup should be taken first). The sibling list is full of plausible alternatives, but the definition gives no routing signal.

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