Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-move

Idempotent

Moves a MariaDB database instance to another Dokploy environment using its database ID and target environment ID.

Instructions

POST /mariadb.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": {
      "mariadbId": "<mariadbId>",
      "targetEnvironmentId": "<targetEnvironmentId>"
    },
    "name": "mariadb-move"
  }
}

Input Schema

NameRequiredDescriptionDefault
mariadbIdYes
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 supply openWorldHint and idempotentHint, so the description carries the burden of describing the mutation, and it discloses nothing. It says nothing about whether data follows the instance, whether downtime or a restart occurs, what permissions are needed, or what happens to the source environment. The endpoint-style text adds zero behavioral context beyond the 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 brief, but the brevity is under-specification rather than economy: a single HTTP route line that conveys no information an agent could not already derive from the tool name. Nothing is front-loaded because there is no content to front-load.

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?

This is a destructive-capable move operation with no output schema, zero parameter documentation, and only minimal annotations, so the definition should be doing substantial explanatory work. Instead it is effectively a bare endpoint stub, leaving the agent unable to call it correctly or predict its effects.

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 two required parameters, mariadbId and targetEnvironmentId, so the description was the only place to explain their meaning and format. It provides none, leaving the agent to infer whether the identifiers are UUIDs, names, or environment slugs.

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 /mariadb.move", which restates the tool name and HTTP verb rather than stating in plain terms what the operation does. An agent can infer that a MariaDB instance is moved somewhere, but the resource scope and the effect on the instance are never spelled out, and it is indistinguishable from siblings such as mysql-move or postgres-move.

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 mention of any alternative such as mariadb-deploy or mariadb-rebuild. The agent must guess the conditions under which moving an instance is the right action.

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