Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-create

Creates a MySQL database service in a Dokploy environment, provisioning the database, user, and credentials for application use.

Instructions

POST /mysql.create

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": {
      "name": "<name>",
      "environmentId": "<environmentId>",
      "databaseName": "<databaseName>",
      "databaseUser": "<databaseUser>",
      "databasePassword": "<databasePassword>"
    },
    "name": "mysql-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
appNameNo
serverIdNo
descriptionNo
dockerImageNomysql:8
databaseNameYes
databaseUserYes
environmentIdYes
databasePasswordYes
databaseRootPasswordNo

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?

The only annotation is openWorldHint=true; the description adds nothing beyond it. For a provisioning mutation that accepts databasePassword and databaseRootPassword, it says nothing about side effects, required permissions, whether the instance is started on creation, how secrets are handled, or how long the operation takes.

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 with zero wasted sentences, but that is under-specification rather than conciseness. The single line is an endpoint signature, not an agent-facing explanation, and there is no front-loaded statement of intent.

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?

A 10-parameter creation tool with 5 required fields, no output schema, and no annotations beyond openWorldHint requires substantial description. Nothing is provided about the created resource, its lifecycle, or the meaning of required inputs, leaving the agent unable to call it safely.

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% across 10 parameters, so the description carries the full burden and fails completely. It never explains name vs appName vs databaseName, the dockerImage default, serverId/environmentId selection, or the difference between databasePassword and databaseRootPassword.

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.create" only restates the tool name as an HTTP verb+path. It implies a create operation on a MySQL resource, but never states what is actually created (a database container? a service instance?), nor what distinguishes it from siblings such as mariadb-create or mysql-deploy.

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 at all: no prerequisites, no exclusions, and no pointer to related tools like mysql-update, mysql-start, or mariadb-create. The agent must infer invocation conditions entirely from the tool name.

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