Skip to main content
Glama
MCP Dokploy Online
by igoruam

destination-remove

Destructive

Deletes a Dokploy destination using its destinationId, enabling users to remove unused or incorrect deployment targets from their infrastructure configuration.

Instructions

POST /destination.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": {
      "destinationId": "<destinationId>"
    },
    "name": "destination-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
destinationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known, but the description adds nothing beyond that: it does not say whether the removal is permanent, whether dependent resources (backups, deployments, mounts) are affected, or whether confirmation is expected. For a destructive operation the description should disclose consequences.

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?

The text is short but it is under-specification rather than conciseness: a bare endpoint string with no front-loaded statement of intent. Nothing is wasted because nothing useful is present.

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 tool with an undocumented required parameter and no output schema, the description should explain effects and return behavior. A route string alone leaves every question an agent would need answered unaddressed.

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% and the single parameter destinationId is undocumented in both schema and description. The description does not say where an ID comes from (e.g., destination-all) or what format it takes, so it adds no meaning beyond the parameter name.

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 the HTTP route "POST /destination.remove", which restates the tool name rather than stating what the tool does. It conveys deletion of a destination only by inference from the name, and gives no scope, effect, or contrast with siblings like destination-update or destination-create.

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, no prerequisites, and no mention of when not to call it or what alternative exists for detaching versus deleting. The agent must infer everything from the name and the sibling list.

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