Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-rebuild

Idempotent

Rebuild a PostgreSQL database instance in Dokploy by providing its postgresId to restore or recreate the database when needed.

Instructions

POST /postgres.rebuild

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-rebuild"
  }
}

Input Schema

NameRequiredDescriptionDefault
postgresIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations only declare openWorldHint and idempotentHint; they say nothing about destructiveness or downtime. The description adds zero behavioral context — it doesn't disclose whether existing data is wiped, whether the instance becomes unavailable during the operation, or what permissions are required. For a 'rebuild' mutation this is a serious omission.

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 that is under-specification rather than conciseness — it contains no substantive content beyond a restated route. There is no front-loaded statement of purpose 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?

For a single-parameter tool that performs a state-altering rebuild, with no output schema and no descriptive annotations beyond idempotency, the definition is completely inadequate. Nothing tells an agent what the operation actually does to the target instance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter, postgresId, with 0% schema description coverage, and the description contributes nothing about its meaning or format. The name is fairly self-evident (the target instance identifier), but the description fails to compensate for the missing schema documentation.

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 route stub "POST /postgres.rebuild", which restates the tool name rather than explaining what a rebuild does. It does not say whether data is preserved, whether the instance is recreated from a backup, or how this differs from siblings like postgres-reload, postgres-start, or postgres-remove.

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 at all — no preconditions, no exclusions, and no pointer to alternatives such as postgres-reload or postgres-changeStatus. An agent has only the tool name to infer intent, which is insufficient for a potentially disruptive 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