Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-changePassword

Idempotent

Change the password for a MySQL database user or root account in Dokploy by specifying the database ID and new password.

Instructions

POST /mysql.changePassword

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>",
      "password": "<password>"
    },
    "name": "mysql-changePassword"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNouser
mysqlIdYes
passwordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already supply idempotentHint and openWorldHint, so the description needed to add the consequential behavior: this is an irreversible credential change affecting a live MySQL instance and likely requires existing access. It discloses none of that, and there is no destructiveHint to fall back on.

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 this is under-specification rather than conciseness; a route stub of four tokens carries no actionable information. No sentence earns its place because no sentence adds meaning beyond the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive credential mutation with three undocumented parameters and no output schema, the definition provides essentially no operational context. An agent could only call it by guessing at mysqlId semantics and the user/root enum.

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 three parameters, and the description names none of them. The critical distinction between the type enum values "user" and "root" (whose password is being changed) and the meaning of mysqlId are left entirely unexplained.

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 "POST /mysql.changePassword", which restates the tool name and HTTP method rather than describing the operation. An agent can infer a MySQL password mutation from the name, but nothing explains scope, target, or how it differs from the many sibling changePassword tools.

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?

There is no when-to-use guidance, no mention of prerequisites such as which credential target to pick, and no pointers to alternatives. The POST verb is the only weak implicit signal that this is a mutating operation.

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