Skip to main content
Glama

Get ACME plugin

proxmox_get_acme_plugin
Read-only

Retrieve one Proxmox ACME challenge plugin's configuration—DNS API, nodes, validation delay—with credential values redacted.

Instructions

Get one ACME challenge plugin's configuration (DNS API, nodes, validation delay). Credential values are redacted.

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": "proxmox_get_acme_plugin"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPlugin ID

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description earns credit beyond that by disclosing that credential values are redacted in the response — a genuine behavioral trait an agent could not infer from structured fields alone — and by naming the categories of content returned.

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?

A single dense sentence with the resource and scope stated first and the redaction caveat second; every clause carries information and nothing is padding.

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

Completeness4/5

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

For a one-parameter read tool with no output schema, the description covers what is fetched, the main content categories, and the important caveat that credentials come back redacted. Only the absence of any note on how to obtain the plugin ID or on error behavior when the ID is unknown keeps it from full completeness.

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 description coverage is 100% and the single 'id' parameter is documented as 'Plugin ID'. The description adds no format, casing, or sourcing hints for the ID (e.g., where to obtain it), so it sits at the baseline for a fully documented schema.

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 pairs a specific verb ('Get') with a specific resource ('one ACME challenge plugin's configuration') and enumerates the content returned (DNS API, nodes, validation delay). The word 'one' implicitly separates it from the plural listing sibling proxmox_list_acme_plugins, though no sibling is named explicitly.

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?

Retrieval of an existing plugin's config is implied by 'Get one ... configuration', and the required 'id' parameter makes the precondition obvious. There is no explicit statement of when to prefer this over proxmox_list_acme_plugins or proxmox_get_acme_account, and no exclusion 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