Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

retry_certificate

Retry a failed managed certificate issuance or renewal after correcting the reported status error, so DNS validation or CA issues can be resolved and the certificate request reattempted.

Instructions

Retry a failed issuance or renewal of a managed certificate (only when status.issuance or status.renewal is "failed"; see status.error for the cause and fix it first). Managed (Let's Encrypt) certificates are validated via DNS: every domain must be in a PRIMARY Hetzner DNS zone (create_zone) that is delegated to Hetzner's nameservers at the registrar, and any CAA record must allow Let's Encrypt. Typical failures: dns_zone_not_found, dns_zone_is_secondary_zone, could_not_verify_domain_delegated_to_zone, caa_record_does_not_allow_ca, ca_dns_validation_failed, Let's Encrypt rate limits. Returns an Action (poll get_action)

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": {
      "id": "<id>"
    },
    "name": "retry_certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCertificate ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it explains DNS validation requirements, CAA constraints, common failure causes, and Let's Encrypt rate-limit risk. It also discloses that the tool returns an Action that must be polled with get_action.

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?

The purpose and failed-state precondition are front-loaded, and all content is relevant. The second sentence is dense with a long list of failure codes, but it is useful context rather than filler.

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

Completeness5/5

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

For a complex external certificate retry with no output schema, the description supplies prerequisites, failure diagnostics, rate-limit caveats, and return behavior. An agent has enough information to decide when to retry and how to handle the resulting Action.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage and fully documents the single id parameter as the certificate ID. The description does not add further parameter-level meaning, so the schema-sufficient baseline applies.

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

Purpose5/5

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

The description states a specific verb and resource: retrying a failed issuance or renewal of a managed certificate. It also clearly scopes the operation to failed certificate states and distinguishes it from creation/update siblings by focusing on retry.

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

Usage Guidelines5/5

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

It gives an explicit precondition: use only when status.issuance or status.renewal is "failed", and inspect/fix status.error first. It also names create_zone as a prerequisite for DNS-zone problems, giving the agent concrete routing guidance.

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