Skip to main content
Glama
Sign In
Dokploy MCP Server

Dokploy MCP Server

by bravos2k5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

previewDeployment-delete

Destructive

Deletes a specified preview deployment using its unique identifier.

Instructions

POST /previewDeployment.delete

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": {
      "previewDeploymentId": "<previewDeploymentId>"
    },
    "name": "previewDeployment-delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
previewDeploymentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.29.1

TDQS

D1.1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds no behavioral context beyond what the annotations already hint (destructiveHint, openWorldHint). It lacks details on irreversibility, confirmation requirements, or side effects, leaving the agent to guess about the operation's full impact.

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?

While the description is short, it is severely under-specified. It provides only a raw endpoint string, which is not concise but rather incomplete. Every sentence should add value; here, the single statement is essentially useless.

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 delete operation with one parameter, a minimal description could still clarify scope and result. This description lacks any completion regarding return values, side effects, or dependencies. It is wholly inadequate for an AI agent to use correctly.

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 input schema has one parameter (previewDeploymentId) with 0% schema description coverage. The description does not explain what this ID represents, how to obtain it, or any constraints (e.g., valid format). The parameter's meaning is entirely opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a tautology ('POST /previewDeployment.delete') that merely restates the HTTP method and endpoint. It does not convey what the tool does beyond what the name implies, nor does it specify the resource scope.

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?

No guidance is provided on when to use this tool versus alternatives like previewDeployment-redeploy or previewDeployment-one. The description fails to indicate prerequisites, effects on related resources, or exclusions.

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