Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-move

Idempotent

Move a Dokploy application to another environment by providing its application ID and the target environment ID through the POST /application.move endpoint.

Instructions

POST /application.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": {
      "applicationId": "<applicationId>",
      "targetEnvironmentId": "<targetEnvironmentId>"
    },
    "name": "application-move"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes
targetEnvironmentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations only declare openWorldHint and idempotentHint, so the description must carry the behavioral burden for what is clearly a mutation, and it does not. Nothing about whether the app is stopped/restarted, what configuration is preserved or lost, required permissions, or failure modes such as a target environment already hosting the app. It does not contradict the annotations, but it adds no context beyond them.

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 not concise in any useful sense — it is an unelaborated route string with no front-loaded purpose, no verb-plus-resource statement, and no structure an agent can act on. The brevity reflects under-specification, not efficiency.

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 destructive-in-practice mutation with two required, fully undocumented parameters and no output schema, the description supplies essentially none of the information needed to invoke it safely. An agent cannot tell what will change, what will be lost, or what a successful call 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 both required parameters, and the description does not mention applicationId or targetEnvironmentId at all. Nothing clarifies identifier format, whether the target environment must be empty or pre-created, or what happens to existing deployments.

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 just the HTTP route "POST /application.move", which restates the tool name without stating what is being moved or what the operation accomplishes. An agent learns only that this is an HTTP endpoint, not how it differs from sibling move tools such as compose-move or postgres-move.

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 prerequisites, and no exclusions — nothing says when to choose application-move over redeploy, saveEnvironment, or any other sibling. A raw endpoint string provides no routing signal at all.

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