Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-create

Creates a PostgreSQL database in a Dokploy environment from required database name, user, password, and environment ID.

Instructions

POST /postgres.create

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": {
      "name": "<name>",
      "databaseName": "<databaseName>",
      "databaseUser": "<databaseUser>",
      "databasePassword": "<databasePassword>",
      "environmentId": "<environmentId>"
    },
    "name": "postgres-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
appNameNo
serverIdNo
descriptionNo
dockerImageNopostgres:18
databaseNameYes
databaseUserYes
environmentIdYes
databasePasswordYes

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?

The only annotation is openWorldHint=true; nothing states that this provisions a real, billable, persistent resource, whether the operation is async/long-running, what happens on partial failure, or how the supplied databasePassword is handled. For a mutation with essentially no annotation coverage of side effects, the description carries the full burden and fails to meet it.

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 that brevity reflects under-specification rather than conciseness; a bare route string is not a useful front-loaded summary of anything an agent needs.

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 9-parameter provisioning tool with required credentials, no output schema, and near-zero annotation coverage, an agent cannot determine return shape (does it return an ID? status?), timing, or failure modes. The definition is completely inadequate for the tool's complexity.

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 9 parameters (5 required), and the description adds no meaning whatsoever — nothing about environmentId's role, dockerImage defaults, serverId nullability, or appName's 63-char constraint origin. This is the worst case for this dimension.

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.create" merely restates the tool name with an HTTP verb; it conveys 'create a postgres thing' but says nothing about what a Postgres resource is here (a managed database instance? a cluster?) or how it differs from siblings like mariadb-create or postgres-deploy. It is effectively a tautology on the name.

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 guidance at all on when to use this versus alternatives: no mention of prerequisites, no distinction from postgres-deploy, postgres-update, or other -create tools, and no note on what must exist beforehand (e.g. environmentId referring to an existing environment).

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