Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-changePassword

Idempotent

Changes the password for a specified PostgreSQL database in Dokploy using its postgresId and a new password to rotate database credentials.

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

NameRequiredDescriptionDefault
passwordYes
postgresIdYes

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 idempotentHint and openWorldHint; the description adds nothing about whether the password change disrupts connections, requires a restart, affects credentials stored elsewhere, or how failures are reported. For a mutating credential operation this is a complete 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 conciseness: a bare route string earns no space because it conveys almost nothing beyond the name.

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?

A two-parameter mutating credential tool with no output schema and no annotation for destructiveness needs far more: what the password change affects, required permissions, and expected result. None of that is present.

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%, so the description must compensate, yet it never mentions postgresId or password, their formats, or constraints beyond minLength.

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 /postgres.changePassword" only restates the tool name and HTTP verb; it names the resource implicitly through the identifier but adds no description of what the operation actually does to the Postgres instance.

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 guidance on when to use this versus the sibling changePassword tools for mariadb/mongo/mysql/redis, no prerequisites, no mention of when not to use it.

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