Skip to main content
Glama
MCP Dokploy Online
by igoruam

certificates-create

Create and upload a custom SSL/TLS certificate to Dokploy for an organization or server, with optional auto-renew and certificate path settings.

Instructions

POST /certificates.create

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": {
      "name": "<name>",
      "certificateData": "<certificateData>",
      "privateKey": "<privateKey>",
      "organizationId": "<organizationId>"
    },
    "name": "certificates-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
serverIdNo
autoRenewNo
privateKeyYes
certificateIdNo
organizationIdYes
certificateDataYes
certificatePathNo

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?

The only annotation is openWorldHint=true and a title, leaving the full behavioral burden on the description, which discloses nothing. It does not say whether the private key is stored, whether a certificate is validated against the organization, whether autoRenew defaults, or what happens on duplicate certificateId.

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 brevity here is under-specification rather than conciseness — a single route string that carries no usable information for the caller.

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 an eight-parameter mutation involving secrets (privateKey) and no output schema, the description should explain required vs optional semantics, secret handling, and return shape. None of that is present.

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?

Eight parameters with 0% schema description coverage and four required fields (name, certificateData, privateKey, organizationId) that receive no explanation anywhere. The description adds nothing about format, e.g. PEM encoding of certificateData/privateKey, the relationship between certificateId and certificatePath, or serverId scoping.

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.create" restates the tool name as an HTTP route. It technically implies a create operation on the certificates resource, but gives no indication of what is being created (a TLS certificate record? a CA-issued cert?) or how it differs from certificates-update or certificates-one beyond the verb.

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 prerequisites, and no mention of alternatives such as certificates-update or certificates-one. An agent must infer everything from the sibling naming convention.

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