Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-clearDeployments

Idempotent

Clears deployment records for a Dokploy compose service using its compose ID, so you can reset or remove outdated deployment history.

Instructions

POST /compose.clearDeployments

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>"
    },
    "name": "compose-clearDeployments"
  }
}

Input Schema

NameRequiredDescriptionDefault
composeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations supply openWorldHint=true and idempotentHint=true, but the description adds nothing — notably it never discloses that a 'clear' operation is destructive, nor whether it cancels running deployments, removes history, or requires authorization. For a mutation tool, the description contributes zero behavioral context.

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 the brevity reflects under-specification rather than efficient communication; the single line is a route string with no front-loaded purpose statement 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?

With no output schema, sparse annotations, and 0% parameter description coverage, the description is the only channel for explaining behavior — and it conveys nothing beyond the endpoint. It is wholly inadequate for a destructive deployment-management operation.

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 the single required composeId parameter, so the description must carry the meaning — but it never mentions the parameter at all. The identifier is inferable from the field name, which keeps this from a 1.

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 only an HTTP route string, 'POST /compose.clearDeployments', which restates the tool name rather than explaining what clearing deployments does (delete deployment history? stop active deployments? free resources?). Nothing distinguishes it from siblings like compose-cancelDeployment, compose-killBuild, or application-clearDeployments.

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 indication of how this differs from the several sibling tools that also affect deployments. The agent is left to guess entirely 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