Skip to main content
Glama
Sign In
Dokploy MCP Server

Dokploy MCP Server

by bravos2k5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mariadb-move

Idempotent

Move a MariaDB instance to a specified target environment. Use this action to relocate databases between environments.

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 observedv0.29.1

TDQS

D1.4/5.0
Behavior2/5

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

Annotations provide idempotentHint: true and openWorldHint: true, but the description adds no behavioral context beyond that. It does not explain what happens during the move (e.g., whether the original is deleted, if downtime occurs, or authorization requirements). No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (6 words) but under-specifies the tool. It does not earn its place because it provides no useful information beyond the tool name and HTTP method. True conciseness would include essential details.

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?

Given no output schema and a move operation, the description should explain what 'move' entails, such as changing environments, impacts on availability, or prerequisites. The description is completely inadequate for an agent to use this tool correctly.

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 coverage is 0% (no descriptions for mariadbId or targetEnvironmentId). The description does not add any meaning or constraints for the parameters. The parameter names are self-explanatory, but without additional context, the agent lacks guidance on valid values or requirements.

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

Purpose1/5

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

The description is just 'POST /mariadb.move', which is a tautology of the name. It does not state what the tool does, leaving the agent to infer from the name alone. No verb or resource explanation is given.

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 on when to use this tool vs alternatives like mariadb-create, mariadb-deploy, or other database move tools (compose-move, mongo-move). The name implies moving a MariaDB instance, but there is no explicit context or exclusion criteria.

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