Skip to main content
Glama
MCP Dokploy Online
by igoruam

certificates-update

Idempotent

Update an existing TLS certificate's name, certificate data, or private key by its ID to correct or renew credentials for Dokploy deployments.

Instructions

POST /certificates.update

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-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
privateKeyNo
certificateIdYes
certificateDataNo

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 supply only openWorldHint and idempotentHint; the description adds nothing beyond them. It does not disclose what an update changes, whether privateKey replacement invalidates existing certificates, whether omitted fields are cleared or preserved, or what permissions are required — serious gaps for a mutation tool.

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 technically short, but the brevity is under-specification rather than efficiency — a bare route string with no front-loaded statement of intent or effect.

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 four-parameter mutation with no output schema and only weak annotations, the description is wholly inadequate. An agent cannot determine what an update does, what state results, or how to safely call it.

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% across four parameters, and the description compensates for none of it. Nothing explains the interaction between certificateData, privateKey, and name, or whether supplying only certificateId is meaningful.

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 /certificates.update", which merely restates the tool name in HTTP notation. It conveys no resource meaning beyond what the name already implies and does nothing to distinguish this from siblings like certificates-create or certificates-all.

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 versus certificates-create, certificates-one, or certificates-remove, nor any mention of prerequisites or preconditions for updating a certificate.

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