Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-remove

Destructive

Removes a PostgreSQL database from Dokploy using its database ID. Use it to delete an existing Postgres instance and free associated resources.

Instructions

POST /postgres.remove

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

Input Schema

NameRequiredDescriptionDefault
postgresIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows this is a destructive operation. The description adds nothing beyond that: it does not say whether the database data, backups, or volumes are destroyed, whether the action is reversible, or what happens to dependent deployments. For a destructive mutation this is a substantial 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 a single short string, so there is no verbosity to trim, but brevity here comes from under-specification rather than efficiency. It is not front-loaded with any actionable meaning.

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 destructive, irreversible-sounding removal tool with no output schema, no annotations explaining consequences, and a bare endpoint restatement leaves the agent without what it needs to call this safely. At minimum it should state what is destroyed and any confirmation or precondition.

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 one required parameter, postgresId, at 0% schema description coverage, so the description must compensate and it does not. The field name makes the intent inferable, but the description gives no format, source, or lookup hint for obtaining the identifier.

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 REST endpoint string "POST /postgres.remove", which restates the tool name rather than stating in prose what the tool does. An agent can infer removal of a Postgres resource, but nothing distinguishes this from sibling removers like cluster-remove or mariadb-remove beyond the URL fragment.

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 alternatives such as postgres-stop (a reversible stop) versus this removal. The agent gets zero routing information.

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