Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-start

Idempotent

Starts a PostgreSQL database instance in Dokploy by its ID, letting you resume stopped database services and restore availability.

Instructions

POST /postgres.start

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

Input Schema

NameRequiredDescriptionDefault
postgresIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already provide openWorldHint=true and idempotentHint=true, so idempotency needs no restating. The description adds nothing about whether starting blocks until ready, startup latency, or behavior when the instance is already running or missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is very short with no filler, but the brevity comes from under-specification rather than economy of expression. The single sentence is front-loaded only because there is nothing else.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a lifecycle operation with no output schema and no documented parameters, the description should explain the resulting state and any preconditions. Nothing beyond the endpoint path is provided.

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?

Schema description coverage is 0% and the one parameter postgresId is documented only as a non-empty string. The description does not clarify that it identifies the target instance or that it is required.

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.start" restates the tool name as an HTTP route rather than describing what the tool does. There is no verb+resource outcome statement; the agent must infer that this starts a Postgres instance, and siblings like postgres-stop are not differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, prerequisites, or alternatives are given. The description does not state what state the instance must be in, nor does it hint at the inverse tool postgres-stop.

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