Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-move

Idempotent

Moves a MySQL database to a specified target environment by ID, enabling relocation across Dokploy environments without manual reconfiguration.

Instructions

POST /mysql.move

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>",
      "targetEnvironmentId": "<targetEnvironmentId>"
    },
    "name": "mysql-move"
  }
}

Input Schema

NameRequiredDescriptionDefault
mysqlIdYes
targetEnvironmentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations only declare openWorldHint=true and idempotentHint=true; destructiveHint is unset, and the description adds nothing about whether moving an instance causes downtime, data migration, reconfiguration, or irreversible loss of the source binding. For a high-impact relocation operation, the description carries an unfulfilled burden.

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 the brevity is under-specification rather than efficiency: a bare route string conveys no front-loaded purpose, scope, or effect to an agent reading only the definition.

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?

With no annotations covering destructiveness, no output schema, and zero parameter documentation, the description should carry essentially all the semantic load — yet it says nothing beyond the HTTP method. It is wholly inadequate for a two-required-parameter mutation tool.

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% for both required parameters, and the description supplies no compensating meaning for mysqlId or targetEnvironmentId. The agent cannot tell whether targetEnvironmentId is an environment slug, UUID, or name, or what happens if the source and target are identical.

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.move" only restates the tool name as an HTTP route; it never says what a "move" does (relocate a MySQL instance between environments? reattach a volume?). An agent must guess the effect from the name alone, and the sibling set (application-move, compose-move, postgres-move) provides no clarifying contrast.

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 guidance, no prerequisites, and no exclusions. Nothing distinguishes mysql-move from mysql-deploy, mysql-rebuild, or the other *-move siblings, so an agent has no basis for selecting it over alternatives.

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