Skip to main content
Glama
MCP Dokploy Online
by igoruam

certificates-remove

Destructive

Remove a certificate from Dokploy by its certificate ID to delete it from the instance.

Instructions

POST /certificates.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": {
      "certificateId": "<certificateId>"
    },
    "name": "certificates-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
certificateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description's only burden was to add context such as what gets destroyed, whether deletion is reversible, or what permissions are required. It adds none of this; the string merely echoes the endpoint. It does not contradict the annotations, but it contributes zero behavioral information.

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 that brevity is under-specification rather than conciseness. There is no front-loaded statement of intent and no structure beyond a raw HTTP method and 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?

This is a destructive mutation with no output schema, no parameter documentation, and only the bare destructive hint in annotations. For that complexity, the definition leaves an agent without nearly everything it would need to call the tool safely and 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?

Schema description coverage is 0% for a required certificateId parameter, so the description had to compensate and does not. It gives no indication of the identifier format, where it comes from (e.g., certificates-all or certificates-one), or any constraints beyond the schema's minLength: 1.

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 /certificates.remove" is a restatement of the tool name and HTTP route rather than a description of the operation. It implies removal of a certificate, but gives no scope, no target object detail, and nothing to distinguish it from siblings such as certificates-update, certificates-one, or certificates-create.

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 on when to use this tool, when not to, or what alternatives exist. An agent must infer that this deletes an existing certificate and cannot tell from the definition whether prerequisites (existence, ownership, confirmation) apply.

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