Skip to main content
Glama
MCP Dokploy Online
by igoruam

project-remove

Destructive

Deletes a Dokploy project by projectId, removing its associated resources from your deployment infrastructure.

Instructions

POST /project.remove

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": {
      "projectId": "<projectId>"
    },
    "name": "project-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is partly covered structurally. However, the description adds nothing beyond that: it does not state whether removal is permanent, what cascades (environments, deployments, tags, backups), or whether confirmation is required. Nothing contradicts the annotations, but no behavioral context is supplied.

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 short, but the brevity reflects under-specification rather than economy of expression. There is no front-loaded statement of effect or consequence, only routing metadata.

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 destructive, open-world mutation with an undocumented required parameter and no output schema, the description is wholly inadequate. An agent cannot determine impact or recovery from it, so it is not complete enough to invoke safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter projectId, so the description carries the full burden and fails to explain whether the value is a numeric ID, slug, or UUID, or how to obtain it. The parameter name is self-explanatory enough to avoid a 1, but no meaning is added.

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 endpoint string "POST /project.remove", which restates the tool name rather than explaining what the tool does. An agent can infer that a project is removed, but there is no explicit verb-plus-resource statement, no scope, and no differentiation from siblings such as project-update or environment-remove.

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 guidance whatsoever about when to use this tool, when not to, prerequisites, or alternatives. Nothing indicates whether a project must be empty first or how this relates to other removal tools in the catalog.

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