Skip to main content
Glama
MCP Dokploy Online
by igoruam

patch-delete

Destructive

Deletes a Dokploy patch by patchId, removing obsolete configuration changes from your deployment workflow.

Instructions

POST /patch.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": {
      "patchId": "<patchId>"
    },
    "name": "patch-delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/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 covered externally. The description adds essentially nothing beyond the transport method (POST) — no statement of what is destroyed, whether deletion is permanent, whether dependent entities are affected, or whether auth/scoping is required. It does not contradict the annotations, but for a destructive operation this is a near-total gap.

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 with no filler, but that brevity reflects under-specification rather than economy. A raw endpoint path is not a front-loaded explanation of intent.

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 a required identifier and no output schema, the definition supplies no information about effect, irreversibility, or required permissions. An agent cannot safely call this from the description alone.

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 patchId, and the description never mentions it. With one undocumented parameter and no compensating text, the definition leaves the agent to infer the identifier's origin and format from the schema name alone.

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 /patch.delete" only restates the tool name as an HTTP route; it never states in prose what the tool does (delete a patch resource) or what a patch is. The verb 'delete' is implied by the name segment, not described, so the definition is effectively a tautology.

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 mention of alternatives such as patch-update, patch-toggleEnabled, or the many other *-delete siblings. An agent gets no basis for choosing this tool over any sibling.

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