Skip to main content
Glama

List ACME directories

proxmox_list_acme_directories
Read-only

List known ACME CA directories and optionally fetch metadata including terms-of-service URL and external account binding requirement. Fetching a directory requires write access.

Instructions

List the known ACME CA directories (Let's Encrypt production/staging...). With directory, also fetch that CA's metadata: terms-of-service URL (needed to register an account) and whether external account binding is required. Fetching directory makes the node connect to that URL, so it needs write access.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_list_acme_directories"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
searchNo
directoryNoAlso fetch metadata for this directory URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/5.0
Behavior4/5

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

The description adds real behavior beyond the annotations: fetching `directory` causes the node to connect out to that URL and requires elevated privilege. That egress detail is genuinely useful and is not recoverable from the schema. One caveat: 'needs write access' sits in tension with readOnlyHint=true, and the external connection sits in tension with openWorldHint=false, so the phrasing could confuse an agent about the tool's side effects.

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 core action before the optional-mode detail; nothing is wasted. Minor cost is that terseness leaves the undocumented `fields`/`search` parameters entirely unaddressed.

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

Completeness3/5

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

There is no output schema and no annotations about return values, so the description carries the burden of describing results, yet it only sketches metadata for the `directory` case and says nothing about the shape of the directory list itself. Combined with two undocumented parameters, an agent can call it but must guess at `fields`/`search` and the response format.

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?

Schema coverage is only 33%, and `fields` and `search` are undocumented in both schema and description. The description does earn credit for `directory` by explaining what metadata it retrieves (ToS URL, external account binding) and its network side effect, but two of three parameters remain unexplained.

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 ('List the known ACME CA directories') and names concrete examples (Let's Encrypt production/staging), which separates it from sibling listing tools such as proxmox_list_acme_accounts or proxmox_list_acme_plugins. It also explains the second mode (metadata fetch via `directory`), though it never explicitly states the contrast with those siblings.

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

Usage Guidelines4/5

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

It gives a clear use context for the optional parameter: pass `directory` when you need the terms-of-service URL 'needed to register an account' or need to know whether external account binding is required. That is actionable when-to-use guidance. It lacks an explicit 'do not use this when...' or a pointer to which sibling to use instead for accounts/plugins.

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