Skip to main content
Glama

List ACME challenge plugins

proxmox_list_acme_plugins
Read-only

List a Proxmox cluster's ACME challenge plugins by DNS or standalone type, showing plugin fields with credential values redacted.

Instructions

List the cluster's ACME challenge plugins (standalone HTTP and DNS API plugins). Credentials in plugin data are redacted; only their keys are shown.

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_plugins"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly plugins of this type
fieldsNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine value beyond that: plugin credentials are redacted and only their keys appear, which tells the agent it cannot retrieve secrets through this tool and should not attempt to read them from the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two short sentences, the subject is front-loaded, and the redaction caveat follows the scope statement. Nothing is wasted or repeated from structured fields.

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?

For a read-only list tool with no output schema, the description covers scope and the credential-redaction caveat, which is the most important return-value fact. It remains incomplete on the two undocumented filter parameters ('fields' and 'search') and on pagination or result shape.

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 description coverage is only 33%: the 'type' enum is documented, but 'fields' (an array of strings) and 'search' (a string) have no schema descriptions. The description supplies no alternative filtering by DNS vs standalone, what 'fields' selects, or what 'search' matches, so the meaning of two of three parameters is left entirely undefined.

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 names a specific verb and resource ("List the cluster's ACME challenge plugins") and scopes it by naming the two plugin kinds it covers (standalone HTTP and DNS API). It is clear what the tool returns, though it does not explicitly contrast itself with the singular sibling proxmox_get_acme_plugin.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. The agent has to infer that it should call this to enumerate plugins and proxmox_get_acme_plugin to inspect one, but the description never says so.

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