Skip to main content
Glama
MCP Dokploy Online
by igoruam

patch-create

Creates a patch definition with specified content and operation for a Dokploy application or compose, enabling controlled configuration changes by file path.

Instructions

POST /patch.create

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": {
      "filePath": "<filePath>",
      "content": "<content>"
    },
    "name": "patch-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
contentYes
enabledNo
filePathYes
composeIdNo
applicationIdNo

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?

The only annotation is openWorldHint=true, which signals external interaction but explains nothing about mutation semantics, permission needs, or side effects. The description adds no behavioral context whatsoever — it does not say whether this writes to a repository, what happens to existing patches, or what the response contains.

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 description is short but only because it contains no information; it is under-specified rather than concise. A bare endpoint string is not front-loaded useful content.

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 tool with six undocumented parameters, no output schema, and a mutation implied by the name, the description is completely inadequate. Nothing an agent needs in order to call this correctly is present.

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?

Six parameters with 0% schema description coverage and the description contributes nothing — not even which of filePath, content, type, enabled, composeId, or applicationId matter. The required filePath/content pair and the create/update/delete enum are left entirely unexplained, despite type='create' on a tool named patch-create being genuinely ambiguous.

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 /patch.create", which restates the tool name in URL form rather than saying what the tool does. An agent learns nothing about what a patch is here, whether it creates a file-patch entity, a repo patch record, or an application patch, nor how it differs from sibling tools like patch-update or patch-create alternatives.

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 any alternative such as patch-update or patch-byEntityId. The agent must guess entirely from the name and schema.

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