Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-delete

Destructive

Deletes a Docker Compose stack in Dokploy by compose ID, optionally removing associated volumes.

Instructions

POST /compose.delete

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": {
      "composeId": "<composeId>",
      "deleteVolumes": "<deleteVolumes>"
    },
    "name": "compose-delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
composeIdYes
deleteVolumesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.4/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, and the description adds nothing beyond them — notably it does not disclose that the operation destroys running services or that volumes may be permanently purged. The single most consequential behavioral fact (data loss from deleteVolumes) is absent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but brevity here is under-specification rather than conciseness; the route string is not front-loaded useful information and carries no explanatory content 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, open-world mutation with two required parameters at 0% schema coverage and no output schema, the description provides essentially nothing — no permission requirements, no effect on deployments, no return value expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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, so the description must compensate and does not. The meaning of `deleteVolumes` — whether volume data is irrecoverably destroyed and what false leaves behind — is entirely undocumented, and `composeId` format/scope is unexplained.

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 /compose.delete", which essentially restates the tool name rather than explaining what is deleted, what a compose is here, or what the operation affects. An agent can infer "delete a compose" only from the name, not from any stated verb+resource+scope.

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, no warning about irreversibility, and no mention of alternatives among the many sibling delete tools (e.g. compose-cancelDeployment vs. full deletion). Everything about selection is left to inference.

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