Skip to main content
Glama
MCP Dokploy Online
by igoruam

patch-toggleEnabled

Idempotent

Toggle a patch on or off by patch ID to control whether it is active in Dokploy.

Instructions

POST /patch.toggleEnabled

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>",
      "enabled": "<enabled>"
    },
    "name": "patch-toggleEnabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
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 openWorldHint=true and idempotentHint=true, but the description contributes nothing beyond them. The only added signal is the POST verb, implying a mutation; there is no disclosure of what toggling does to the patch, side effects, permission requirements, or reversibility.

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 a single short line with no wasted words, but this is under-specification rather than conciseness. There is no front-loaded statement of purpose and no structure beyond a raw route path.

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 state-mutating tool with two undocumented required parameters, no output schema, and only partial annotation coverage, the description is wholly inadequate. An agent would have to guess at both the effect of the call and the meaning of its inputs.

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 two required parameters (patchId, enabled), and the description supplies no meaning for either. Constraints such as whether 'enabled' is a set-value or a flip, or what patchId format is expected, remain 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?

The description is only the route signature "POST /patch.toggleEnabled", which essentially restates the tool name. It does hint at verb-plus-resource (toggling an 'enabled' flag on a patch) and the HTTP method, but it never states in prose what the tool actually does or distinguishes itself from siblings such as patch-update or domain-toggleEnable.

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 conditions, and no mention of alternatives. An agent cannot tell from this string whether patch-toggleEnabled is the right way to enable or disable a patch versus using patch-update or patch-delete.

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