Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-deploy

Idempotent

Deploys a PostgreSQL database instance in Dokploy by ID, allowing users to provision and manage Postgres infrastructure through the MCP server.

Instructions

POST /postgres.deploy

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

Input Schema

NameRequiredDescriptionDefault
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 already declare openWorldHint=true and idempotentHint=true, so safety/idempotency is covered structurally. The description adds nothing beyond that: no statement of what gets created or destroyed, how long it takes, whether it blocks, or what state the instance must be in beforehand.

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 the brevity is under-specification rather than economy; the one line conveys only the transport method and no front-loaded purpose.

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 mutating deploy operation with a required identifier, no output schema, and zero parameter documentation, the description is completely inadequate. An agent has no basis to call this correctly or to know what result to expect.

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 single required parameter postgresId has 0% schema description coverage, so the description carries the full burden of explaining it, yet says nothing about its format or where to obtain it. No meaning is added beyond the bare property name.

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 just the HTTP verb and the route path, 'POST /postgres.deploy', which restates the tool name rather than explaining what deploying a Postgres instance actually does (provision? restart with new config? apply changes?). It does not distinguish this from siblings like postgres-rebuild or postgres-start.

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 tool. An agent cannot tell from this text whether to deploy, rebuild, or start a Postgres instance.

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