Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-rebuild

Idempotent

Rebuild a Dokploy MySQL instance using its ID to recover or recreate the database service after failure or required configuration changes.

Instructions

POST /mysql.rebuild

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-rebuild"
  }
}

Input Schema

NameRequiredDescriptionDefault
mysqlIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations supply only idempotentHint and openWorldHint; there is no destructiveHint, so the agent's entire behavioral picture comes from the description, which says nothing about data loss, downtime, permission requirements, or whether configuration/environment variables survive. Zero context is added beyond annotations.

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 efficient; a bare route string conveys no information an agent could act on beyond the title.

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 likely destructive lifecycle operation on a database instance, the definition leaves out every fact an agent needs: what is rebuilt, what is lost, whether it is reversible, and what the tool returns. Idempotency annotation alone is far too thin.

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% and the single parameter 'mysqlId' is undocumented in both schema and description. The name is largely self-explanatory as a resource identifier, but the description adds no format, source, or validation detail to compensate for the coverage 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?

"POST /mysql.rebuild" only restates the tool name and its HTTP route; it never says what rebuilding a MySQL instance means (recreate container? reinstall? wipe data?). The sibling set (postgres-rebuild, redis-rebuild, etc.) shows the family, but nothing distinguishes this tool's effect.

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?

No when-to-use guidance, no prerequisites, no exclusions, and no comparison to adjacent tools like mysql-reload, mysql-start, or mysql-create, which an agent would plausibly confuse with it.

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