Skip to main content
Glama

List appliance templates

proxmox_list_appliance_templates
Read-only

Lists downloadable LXC container templates from the Proxmox appliance index, with filters for node, section, search, and result limit, to help you select one for download.

Instructions

List the LXC container templates available for download from the Proxmox appliance index (Debian, Ubuntu, Alpine..., and TurnKey apps). Download one with proxmox_download_appliance_template. If the list is empty, the node may need pveam update.

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

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
limitNoMaximum number of results (default 200)
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
sectionNoOnly this section, e.g. "system" or "turnkeylinux"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the mutation profile is covered; the description adds useful behavior the annotations do not: this is a downloadable catalog, and an empty result may indicate a stale index needing `pveam update`. It does not disclose pagination behavior despite a limit parameter, which keeps it shy of a 5.

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?

Three short sentences, front-loaded with the purpose, then the actionable follow-up, then the troubleshooting caveat. No filler or redundancy.

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 read-only list tool with no output schema, the definition covers source, follow-up and the empty-result case. Minor gaps remain around whether the list is the node's cached index versus a live remote fetch, which matters for expectations about freshness.

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 80%, so the schema already documents node, limit, fields, search and section. The description adds no parameter-level detail (no mention of section values, search behavior, or the default 200 limit), so the baseline 3 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?

States a specific verb and resource ("List the LXC container templates") plus the source ("Proxmox appliance index") and the content domain (Debian, Ubuntu, Alpine, TurnKey). An agent can readily separate this catalog listing from proxmox_list_containers or proxmox_list_guests.

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?

Explicitly routes the agent to proxmox_download_appliance_template as the follow-up action and adds a diagnostic note for an empty result ("the node may need `pveam update`"). It gives clear context but no explicit when-not guidance or other alternatives.

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