Skip to main content
Glama
MCP Dokploy Online
by igoruam

patch-saveFileAsPatch

Idempotent

Save a file as a patch for a Dokploy application or compose service by providing the file path, content, and create/update mode.

Instructions

POST /patch.saveFileAsPatch

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

Input Schema

NameRequiredDescriptionDefault
idYes
typeYes
contentYes
filePathYes
patchTypeNoupdate

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 openWorldHint=true and idempotentHint=true, and the description adds nothing to that picture beyond the bare HTTP verb POST, which implies a write. It never explains what the 'application' versus 'compose' types mean behaviorally, whether an existing patch is overwritten, or what side effects occur on the patch repository.

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 not concise in the useful sense: it is a single route signature with no front-loaded explanation of purpose. Brevity here reflects under-specification rather than economy, since no sentence conveys actionable information.

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?

This is a mutating, four-required-parameter tool with 0% schema description coverage and no output schema, so the description carries the full explanatory burden and delivers none of it. An agent would have to guess at required value formats, enum semantics, and the effect of the save.

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% across 5 parameters, including two enum parameters (type: application|compose, patchType: create|update), and the description explains none of them. The distinction between patchType=create and patchType=update and the meaning of filePath relative to the patch repo are entirely undocumented.

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.saveFileAsPatch" only restates the tool name as an HTTP route; it never says what a patch is, what a file is being saved from, or what the resulting patch contains. An agent cannot distinguish it from siblings like patch-create or patch-update without opening the schema.

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 mention of alternatives such as patch-create or patch-update, and no prerequisites or preconditions stated. Nothing tells the agent under which circumstances this endpoint is the right choice.

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