Skip to main content
Glama

create-certificate

create-certificate

Create SSL/TLS certificates for domains via automatic Let's Encrypt provisioning or manual upload to secure Nginx Proxy Manager hosts.

Instructions

Create a new certificate. Let's Encrypt is supported for automatic provisioning. Manual provider requires two-step workflow not exposed here.

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": {
      "instanceName": "<instanceName>",
      "provider": "<provider>",
      "domainNames": "<domainNames>",
      "niceName": "<niceName>"
    },
    "name": "create-certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
niceNameYesHuman-readable name for this certificate
providerYes
domainNamesYesDomain names for the certificate
dnsChallengeNo
instanceNameYes
certificateKeyNoPEM private key for manual provider
letsencryptEmailNo
certificateContentNoPEM certificate for manual provider
letsencryptAgreementNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important behavioral trait: the manual provider's two-step workflow is not exposed here, meaning a manual-provider call is likely incomplete. It says nothing about whether creation blocks on ACME validation, what permissions are needed, error behavior, or what a successful response contains, which is a notable gap for an un-annotated 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and followed by the provider caveat. Every sentence carries information and none is filler; the style is terse but not cryptic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter mutation tool with no annotations and no output schema, the description leaves too much unexplained: required-field relationships, what the returned certificate looks like, and whether provisioning is synchronous. The provider caveat is valuable but does not cover the complexity of the call.

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 coverage is only 44%, and the description compensates only partially by naming the two provider modes and hinting that the manual-provider flow is unsupported. It adds no meaning for letsencryptEmail, letsencryptAgreement, niceName, dnsChallenge, instanceName, or the certificateKey/certificateContent pairing, so most parameters remain undocumented in both places.

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

Purpose4/5

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

The description opens with a specific verb+resource ("Create a new certificate") and immediately distinguishes the two provisioning modes, so the agent knows what is being created and that Let's Encrypt vs manual behave differently. It stops short of naming sibling tools such as renew-certificate or update-proxy-host, so the boundary against those is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Let's Encrypt is supported for automatic provisioning" plus the warning that manual requires a workflow "not exposed here" gives real guidance about which provider to choose and flags that manual creation cannot be completed through this call. There is no explicit statement of when to use this versus renew-certificate or list-certificates, so the guidance is contextual rather than decisive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.