Skip to main content
Glama
MCP Dokploy Online
by igoruam

project-duplicate

Idempotent

Duplicate a Dokploy project environment, copying all or selected services, to create isolated copies for staging, testing, or parallel deployments.

Instructions

POST /project.duplicate

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": {
      "sourceEnvironmentId": "<sourceEnvironmentId>",
      "name": "<name>"
    },
    "name": "project-duplicate"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
descriptionNo
includeServicesNo
selectedServicesNo
sourceEnvironmentIdYes
duplicateInSameProjectNo

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 declare openWorldHint=true and idempotentHint=true, so the description's only contribution is the word POST, weakly signalling a mutation. It does not disclose what is copied, whether the duplicate lands in the same project, or what happens to services when includeServices is true, all of which are non-obvious for a duplication operation.

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 extremely short, but this is under-specification rather than conciseness: a bare route string conveys no information an agent could not derive from the tool name. There is no front-loaded purpose statement or structure to speak of.

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 6-parameter mutation tool with no output schema and only openWorld/idempotent annotations, the definition is completely inadequate. It omits what is duplicated, the meaning of every parameter, and any side effects, leaving the agent unable to invoke it correctly without guessing.

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% across 6 parameters, so the description carries the full burden and provides nothing. Key semantics (sourceEnvironmentId as the project to copy, duplicateInSameProject, selectedServices with its type enum, includeServices defaulting to true) are left completely undocumented.

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 merely the HTTP route "POST /project.duplicate", which restates the tool name rather than explaining what it does. An agent can guess it duplicates a project, but nothing states what a duplicated project contains (services, env vars, settings) or how it differs from the sibling environment-duplicate.

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 mention of alternatives such as environment-duplicate or project-create. The agent must infer entirely from the tool name and the presence of a sourceEnvironmentId parameter.

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