Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-changePassword

Idempotent

Changes the password for a MariaDB user or root account in a Dokploy-managed database using the MariaDB ID and new password.

Instructions

POST /mariadb.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": {
      "mariadbId": "<mariadbId>",
      "password": "<password>"
    },
    "name": "mariadb-changePassword"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNouser
passwordYes
mariadbIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations supply only openWorldHint and idempotentHint, leaving mutating/destructive behavior entirely to the description, which says nothing. It fails to disclose that this alters credentials, whether the old password stops working, or what permissions are required — all critical for a credential-mutation tool with no destructiveHint.

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 it is under-specification rather than conciseness: a method-plus-path string with no front-loaded purpose statement. Brevity here costs the agent all the information it needs.

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 destructive-in-effect credential mutation with three undocumented parameters, no output schema, and minimal annotations, this definition is completely inadequate. An agent could not safely invoke it without guessing at the meaning of the type enum and the impact of the change.

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, so the description must compensate and does not. The 'type' enum (user vs root) is a consequential choice that is never explained, nor are the meaning or constraints of mariadbId and password.

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 verb and path, 'POST /mariadb.changePassword', which essentially restates the tool name. It conveys that a password is being changed but not what that entails, what it applies to, or how it differs from sibling tools like mariadb-update or the other *-changePassword variants.

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 at all: no prerequisites, no mention of when to prefer mariadb-update, and no indication of what happens to existing sessions or credentials. Nothing misleading is stated, but the agent receives zero routing or exclusion help.

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