Skip to main content
Glama
MCP Dokploy Online
by igoruam

patch-update

Idempotent

Create, update, or delete Dokploy patches by patch ID, with content, file path, and enabled status to manage deployment configuration changes.

Instructions

POST /patch.update

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-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
contentNo
enabledNo
patchIdYes
filePathNo
createdAtNo
updatedAtNo

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 openWorldHint=true and idempotentHint=true, so the description's job is to add context such as what gets overwritten, required permissions, or side effects. Instead it contributes nothing beyond an HTTP method token, leaving the mutation's blast radius and semantics completely undisclosed.

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 this is under-specification rather than conciseness; a single route fragment carries no front-loaded purpose or actionable detail.

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 seven-parameter mutation tool with no output schema and no descriptive parameter docs, the definition is far too thin. Nothing tells an agent what a valid invocation looks like, what the enum's create/delete values mean in an "update" endpoint, or what happens to unspecified fields.

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?

Seven parameters exist with 0% schema description coverage, including an enum (create/update/delete) and a required patchId. The description explains none of them and does not even note that patchId is required, so it fails to compensate for the schema gap.

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 "POST /patch.update", which restates the tool name in HTTP-route form rather than stating a verb and resource in plain language. It implies a patch-update mutation, but gives no indication of what aspect of a patch is updated (content, enabled flag, file path, lifecycle timestamps).

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 exclusions, and no mention of alternatives such as patch-toggleEnabled, patch-create, patch-delete, or patch-byEntityId. An agent must guess entirely from the name which sibling to pick.

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