Skip to main content
Glama
MCP Dokploy Online
by igoruam

environment-remove

Destructive

Removes a specified Dokploy environment by its ID, enabling cleanup of unused or obsolete deployment environments.

Instructions

POST /environment.remove

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": "environment-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
environmentIdYes

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 already declare destructiveHint=true and openWorldHint=true, so the agent knows this is a destructive write. The description supplies nothing beyond that — no statement of what is destroyed along with the environment, irreversibility, or required permissions.

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 brevity here reflects under-specification rather than efficiency: a bare HTTP route is not a useful front-loaded summary. A single sentence of plain English would have cost no more space and delivered far more.

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?

This is a destructive, likely cascading operation on a whole environment with an undocumented required identifier and no output schema — exactly the case where the description must carry the burden, and it does not.

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 the single required parameter environmentId, so the description must compensate and does not. It never says what identifier is expected or where to obtain it.

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.remove" merely restates the tool name and an HTTP method/path pair; it adds no plain-language statement of what is being removed or what an "environment" is in this API. An agent can guess it deletes an environment, but that inference comes from the name, not the description.

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?

No when-to-use guidance at all: nothing about prerequisites, whether the environment must be empty, or which sibling to use for related operations such as environment-update or environment-one. The endpoint string provides no selection criteria.

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