Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-update

Idempotent

Update an existing MySQL database service in Dokploy by ID, adjusting image, credentials, resource limits, ports, and deployment settings.

Instructions

POST /mysql.update

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

Input Schema

NameRequiredDescriptionDefault
envNo
argsNo
nameNo
appNameNo
commandNo
mysqlIdYes
cpuLimitNo
replicasNo
createdAtNo
modeSwarmNo
networkIdsNo
descriptionNo
dockerImageNo
labelsSwarmNo
memoryLimitNo
databaseNameNo
databaseUserNo
externalPortNo
networkSwarmNo
ulimitsSwarmNo
environmentIdNo
cpuReservationNo
placementSwarmNo
databasePasswordNo
healthCheckSwarmNo
applicationStatusNo
endpointSpecSwarmNo
memoryReservationNo
updateConfigSwarmNo
restartPolicySwarmNo
rollbackConfigSwarmNo
databaseRootPasswordNo
detachDokployNetworkNo
stopGracePeriodSwarmNo

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 declare openWorldHint=true and idempotentHint=true but say nothing about destructiveness or prerequisites. The description adds zero behavioral context beyond the route string: it does not state that this mutates a running service, whether changes trigger a redeploy, whether omitted fields are reset, or what permissions are needed. For a 34-parameter mutation this is a serious 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?

It is short, but brevity here is under-specification rather than economy: a bare route with no front-loaded statement of purpose or effect. There is no wasted sentence, but also no useful sentence.

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 34 parameters at 0% schema coverage, no output schema, and annotations that omit destructive/permission hints, the description is far from sufficient. An agent has no reliable basis to construct a correct call or predict its 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?

Schema description coverage is 0% across 34 parameters, so the schema supplies bare names and types only (env, args, modeSwarm, placementSwarm, databaseRootPassword, etc.). The description must compensate and instead contributes nothing, leaving critical fields like databaseRootPassword and detachDokployNetwork undocumented in meaning or effect.

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 the HTTP route 'POST /mysql.update'. It does convey a mutation on a mysql resource, but it restates the tool name rather than describing what updating a MySQL service actually entails (config fields, redeploy behavior, etc.). An agent cannot distinguish this from siblings like mysql-saveEnvironment or mysql-changeStatus on the strength of this text alone.

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 whatsoever: no conditions, no prerequisites, no mention of when to prefer mysql-saveEnvironment, mysql-saveExternalPort, or other narrower siblings over a general update. The agent must infer everything from the 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