Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-deploy

Idempotent

Deploys a MySQL database instance on a Dokploy server using its MySQL ID, enabling database provisioning through the MCP interface.

Instructions

POST /mysql.deploy

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

Input Schema

NameRequiredDescriptionDefault
mysqlIdYes

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 supply idempotentHint=true and openWorldHint=true, but the description adds nothing beyond the route – no statement of what gets deployed, whether existing data is replaced, what permissions or plan constraints apply, or how long the operation takes. For a deploy action with no destructive/readOnly hint declared, the omitted blast radius is a significant gap.

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?

At four tokens the text is certainly compact, but its brevity comes from under-specification rather than discipline – it is a route annotation, not a description. There is no front-loaded statement of purpose for an agent to anchor on.

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 output schema, a single undocumented parameter, and only reductive annotations, the description carries the full explanatory burden and delivers none of it. An agent cannot reliably decide when to call this versus mysql-create or mysql-start, nor what to pass as mysqlId.

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?

The single required parameter mysqlId has 0% schema description coverage, and the description never mentions it or explains what it identifies. Nothing in the text compensates for the undocumented schema, so an agent cannot tell whether the ID is a target MySQL instance, a template, or a deployment job.

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 "POST /mysql.deploy" – it restates the tool name plus an HTTP verb, and does not state what deploying actually does (create an instance? apply a config? start a container?). It gives an agent no basis to distinguish it from the many sibling deploy tools (mariadb-deploy, postgres-deploy, compose-deploy) or from adjacent lifecycle tools like mysql-start, mysql-rebuild or mysql-create.

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. The description contains only a route string, so the agent must guess whether this is the initial provisioning call or a re-deploy of an existing instance, which is exactly the ambiguity the sibling names (mysql-create, mysql-start, mysql-rebuild) create.

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