Dokploy MCP Server

postgres-changePassword

Idempotent

Change the password of a PostgreSQL database managed by Dokploy.

Instructions

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

Input Schema

Name	Required	Description	Default
`postgresId`	Yes
`password`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.29.1Jun 13, 2026

TDQS

D1.3/5.0

Behavior2/5

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

Annotations include idempotentHint=true and openWorldHint=true, but the description adds no behavioral context. It does not explain side effects (e.g., password change affects authentication), idempotency implications, or required permissions. With minimal annotations, the description fails to disclose behavioral traits beyond what is already signaled.

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 description is extremely short but at the expense of informativeness. It is not effectively concise because it omits essential purpose and usage details. Being concise should not mean being empty; this description is underspecified.

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 the complexity of a password-changing operation for a database, and with no output schema, the description is completely inadequate. It lacks information about effects (e.g., immediate password update, session invalidation), prerequisites, or postconditions. The tool is not usable based solely on this description.

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 input schema defines two required parameters (postgresId, password) with basic constraints, but schema description coverage is 0%. The description provides no additional meaning or usage hints for these parameters, such as formatting or constraints for the password. The agent relies solely on schema, which lacks semantic guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is 'POST /postgres.changePassword', which merely repeats the tool name and HTTP method. It fails to state what the tool does—it does not mention changing a password or any action. This is a tautology and provides no purpose.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus sibling tools like mariadb-changePassword or mongo-changePassword. There is no context for appropriate usage scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server