Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-changeStatus

Idempotent

Update a PostgreSQL instance's application status in Dokploy by providing its ID and target state (idle, running, done, or error).

Instructions

POST /postgres.changeStatus

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>",
      "applicationStatus": "<applicationStatus>"
    },
    "name": "postgres-changeStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
postgresIdYes
applicationStatusYes

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 supply openWorldHint=true and idempotentHint=true, and the description adds no behavioral context beyond the bare POST verb. It does not explain state transitions, side effects on a running database, required permissions, or whether the change is disruptive; for a mutation endpoint that 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 short, but its brevity comes from under-specification rather than economy; the single fragment conveys only the HTTP method, which the transport already implies.

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?

With no output schema, two undocumented required parameters, and a mutating operation, the definition omits everything an agent would need: effect semantics, permission requirements, and return behavior.

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% for both parameters, so the description must compensate and it does not. Neither postgresId nor applicationStatus is explained, and nothing indicates whether the status change is applied live or requires a restart.

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 "POST /postgres.changeStatus", which restates the tool name and HTTP method rather than stating what the tool actually does. An agent learns nothing about the effect of changing a Postgres application's status, nor what distinguishes this from postgres-update 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 whatsoever, no mention of prerequisites, and no reference to alternatives such as postgres-start, postgres-stop, or postgres-update. The agent must infer everything from the name alone.

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