Skip to main content
Glama
MCP Dokploy Online
by igoruam

patch-cleanPatchRepos

Idempotent

Cleans patch repositories for a specified Dokploy server by server ID, removing stale patch data to keep infrastructure storage consistent.

Instructions

POST /patch.cleanPatchRepos

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "patch-cleanPatchRepos"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/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, so the agent knows the call touches external state and can be retried safely. The description adds nothing beyond that: it does not say what is removed during a clean, whether the action is reversible, or what permissions are needed for a POST that plausibly deletes patch repository data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short but that is under-specification, not conciseness: a bare route string carries no front-loaded purpose or usage signal. Every sentence that would earn its place is missing.

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?

No output schema exists, so the description is fully responsible for conveying behavior, and it conveys none. For a POST operation named "clean" that may destroy data, with an undocumented serverId, the definition is inadequate for correct invocation.

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?

The single parameter serverId has 0% schema description coverage and the description never mentions it. Nothing indicates whether serverId is required for targeting a specific server, what happens when it is omitted (it is optional), or whether it accepts a name or an ID.

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 raw route string "POST /patch.cleanPatchRepos", which restates the tool name rather than explaining what cleaning patch repositories actually does. There is no verb-plus-resource explanation of the effect (pruning stored patch files? resetting repo state?), so the agent cannot distinguish it from siblings such as patch-delete or patch-ensureRepo.

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 at all: no preconditions, no warning about when cleaning is inappropriate, and no pointer to related tools like patch-update or patch-ensureRepo. The only textual content is an HTTP method and path.

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