Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-move

Idempotent

Move a PostgreSQL database to a different Dokploy environment by passing its database ID and the target environment ID.

Instructions

POST /postgres.move

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>",
      "targetEnvironmentId": "<targetEnvironmentId>"
    },
    "name": "postgres-move"
  }
}

Input Schema

NameRequiredDescriptionDefault
postgresIdYes
targetEnvironmentIdYes

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 declare openWorldHint=true and idempotentHint=true, and the description adds no behavioral context whatsoever beyond the verb implied by the name — nothing about downtime, data migration, permissions, or side effects on the source environment. For a mutating relocation operation, this leaves the agent with no disclosure of consequences.

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 comes from having no content rather than from discipline; the single line is a route echo, not a front-loaded purpose statement. Nothing in it earns its place because it conveys no information beyond the tool name.

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?

A parameterized, mutating, open-world operation with no output schema and no annotations covering destructiveness or side effects demands a real description, and this definition supplies none. An agent cannot confirm what gets moved, whether the source is preserved, or what a success response looks like.

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 two required parameters (postgresId, targetEnvironmentId), and the description provides no explanation of either. The meaning of postgresId versus targetEnvironmentId must be guessed entirely from the property names.

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.move", which restates the tool name as an HTTP route rather than explaining the action. It never states that a Postgres instance is being relocated to another environment, and nothing distinguishes it from siblings like application-move, mysql-move, or postgres-rebuild.

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 at all: no prerequisites, no statement of when a move is appropriate versus a rebuild or redeploy, and no mention of the other -move siblings. An agent must infer everything from the name.

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