Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-update

Idempotent

Update an existing PostgreSQL database service in Dokploy by ID, including image, environment variables, resource limits, replicas, and credentials.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
envNo
argsNo
nameNo
appNameNo
commandNo
cpuLimitNo
replicasNo
createdAtNo
modeSwarmNo
networkIdsNo
postgresIdYes
descriptionNo
dockerImageNo
labelsSwarmNo
memoryLimitNo
databaseNameNo
databaseUserNo
externalPortNo
networkSwarmNo
ulimitsSwarmNo
environmentIdNo
cpuReservationNo
placementSwarmNo
databasePasswordNo
healthCheckSwarmNo
applicationStatusNo
endpointSpecSwarmNo
memoryReservationNo
updateConfigSwarmNo
restartPolicySwarmNo
rollbackConfigSwarmNo
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 only supply openWorldHint and idempotentHint, leaving the description to explain what a partial update does to the 33-field configuration — merge vs replace, permission requirements, and side effects on running containers. None of that is disclosed, so the description adds zero behavioral value beyond the annotations.

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 one-liner is short but is under-specification rather than conciseness; it conveys no actionable information. There is no front-loaded statement of intent or effect.

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 33-parameter mutation tool with no output schema, no parameter descriptions, and only two weak annotations needs substantial documentation of scope and consequences. The definition is completely inadequate for the complexity involved.

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 33 parameters (postgresId, env, replicas, swarm sub-configs, resource limits, database credentials), and the description supplies no semantics for any of them. With low coverage the description must compensate, and it does not.

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.update" merely restates the tool name in HTTP-route form; it implies mutation of a Postgres resource but names no fields, scope, or effect. It does nothing to distinguish this from siblings such as postgres-deploy, postgres-changeStatus, or postgres-saveExternalPort, which all mutate the same resource.

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, no prerequisites, and no mention of any alternative among the many postgres-* mutation siblings. An agent has no basis for choosing this tool over postgres-create or application-update.

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