Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-start

Idempotent

Starts a specified MySQL database instance in Dokploy by ID, bringing it online for application and infrastructure use.

Instructions

POST /mysql.start

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

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 only supply openWorldHint and idempotentHint; there is no readOnly or destructive hint for a lifecycle operation that mutates server state. The description does not disclose whether start preserves existing data, what happens if the instance is already running, or whether it blocks until ready.

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?

The text is short but not concise in the useful sense: it is a bare endpoint string with no front-loaded purpose statement. Brevity here reflects under-specification rather than disciplined editing.

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?

For a state-mutating lifecycle tool with an undocumented required parameter, absent readOnly/destructive annotations, and no output schema, the definition is far too thin to let an agent call it correctly or predict side 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?

The single required parameter mysqlId has 0% schema description coverage, so the description must compensate for that gap and it does not. It never explains what mysqlId refers to (instance ID vs name) or the expected format.

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.start" merely restates the tool name as an HTTP method and path; it never says in prose that it starts a MySQL instance. An agent can infer the resource and the verb from the name, but the description itself adds no specificity beyond that.

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 alternatives such as mysql-stop or the other engine start tools. Nothing tells the agent whether this is safe on a running instance or what state it expects.

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