Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-stop

Idempotent

Stops a running PostgreSQL service in Dokploy using its postgres ID, helping you shut down database instances when they are no longer needed.

Instructions

POST /postgres.stop

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

Input Schema

NameRequiredDescriptionDefault
postgresIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations already state idempotentHint=true and openWorldHint=true, and the description adds nothing beyond them: it does not say whether the instance must be running, whether data is preserved, whether downtime is involved, or how to restart it. The description neither contradicts nor enriches the annotations.

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?

The text is short, but its brevity comes from under-specification rather than efficiency — the one line is a route stub, not an explanation, so nothing is front-loaded for the agent.

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 lifecycle-mutating operation that takes down a database instance, the definition omits all operational context: required state, consequences, reversibility, and expected result. Annotations cover only idempotency and open-world access, so the burden falls entirely on a description that provides nothing.

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?

The single required parameter postgresId has 0% schema description coverage, and the description supplies no clarification of its format, source, or whether it is the instance ID versus a name. The parameter name is fairly self-explanatory, which keeps this above the floor, but no added meaning is provided.

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.stop" only restates the tool name and its HTTP method/path. It conveys no resource scope, no verb phrasing an agent can act on, and nothing distinguishes it from siblings such as postgres-start, postgres-reload, or the many *-stop tools.

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 mention of preconditions, and no pointer to alternatives like postgres-reload or postgres-remove for cases where stopping is not the right action.

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