Skip to main content
Glama

renew-certificate

renew-certificate

Renew a Let's Encrypt certificate for a specified Nginx Proxy Manager instance and return the updated certificate details.

Instructions

Renew a Let's Encrypt certificate. Returns the updated certificate details.

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>",
      "id": "<id>"
    },
    "name": "renew-certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
instanceNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden. It only says renewal happens and returns updated details; it says nothing about whether the existing certificate is replaced/invalidated, ACME/Let's Encrypt rate limits, required permissions, or failure modes. For an externally-facing mutation that hits a rate-limited CA, this is a serious gap.

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?

Two short, front-loaded sentences with no filler or redundancy. Brevity is appropriate in form, though it reflects under-specification rather than economy.

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?

A mutation tool with no annotations, no output schema, and two undocumented required parameters requires far more description than two sentences. Only the vague notion of 'updated certificate details' hints at a return value, and nothing explains side effects on the prior certificate.

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 two required parameters ('id' and 'instanceName'), and the description adds no meaning to either. The agent cannot tell whether 'id' is the certificate identifier, a numeric ID, a domain name, or an ARN, nor what an instanceName refers to.

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?

States a specific verb+resource ('Renew a Let's Encrypt certificate'), which is clearly distinct from sibling operations like create-certificate or get-certificate. It does not, however, explain how renewal differs from creating a new certificate or when renewal is appropriate.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites (e.g., must the certificate exist, must it be near expiry), and no alternatives such as delete-certificate+create-certificate. The agent must infer invocation conditions entirely.

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