Skip to main content
Glama
MCP Dokploy Online
by igoruam

environment-duplicate

Idempotent

Duplicates a Dokploy environment by creating a copy with a new name and optional description, enabling reuse of configuration for another deployment.

Instructions

POST /environment.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": {
      "environmentId": "<environmentId>",
      "name": "<name>"
    },
    "name": "environment-duplicate"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
descriptionNo
environmentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the description is not the sole carrier of behavior. Still, it adds nothing: no statement about what gets copied, whether the new environment is started, or what permissions are required for a mutation of this kind.

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?

Brevity here is under-specification rather than conciseness. A single endpoint string is not front-loaded information an agent can act on.

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-adjacent creation/mutation tool with an undocumented three-parameter schema and no output schema, the definition omits everything an agent needs: what is duplicated, side effects, and return shape.

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?

Three parameters with 0% schema description coverage and no additionalProperties nuance explained. The description gives no meaning for environmentId (source) versus name (new environment's name) or for the optional description field, so the agent gets no help where the schema gives none.

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 /environment.duplicate" only restates the tool name in HTTP form. It never says what duplication actually copies (services, variables, settings) or how the result differs from the source environment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of alternatives such as environment-create or project-duplicate. The agent must infer the choice purely from the tool 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