Skip to main content
Glama

List Proxmox options

list_proxmox_options
Read-only

List the provisioning options a Proxmox VE credential can reach: the host nodes (with CPU/memory capacity) and the static instance-type presets ('px-small' to 'px-xlarge'), plus - when a node is given - that node's usable storage pools, network bridges, and clone-source templates. Call this before create_proxmox_cluster: first without a node to pick one, then with the chosen node to pick storage, bridge, and template. Read-only; talks to the customer's Proxmox VE API, so it can take a few seconds.

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": {
      "credential_id": "<credential_id>"
    },
    "name": "list_proxmox_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoOptional Proxmox host node name. When provided, the reply also carries that node's storages, bridges, and templates.
credential_idYesUUID of the Proxmox VE credential.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces it while adding genuinely new context: it talks to the customer's Proxmox VE API and can take a few seconds, which sets latency expectations. It does not cover failure modes (e.g., invalid credential or unreachable node), so it stops short 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.

Conciseness4/5

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

Front-loaded with the resource and its contents, then the workflow, then the read-only/latency note. Dense but every clause carries information; the single long opening sentence is slightly heavy but not padded.

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?

With no output schema, the description compensates by enumerating the return contents for both the node-less and node-scoped cases, plus latency and read-only behavior. An agent has everything needed to call it correctly and interpret the result.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by framing 'node' as a progressive-disclosure switch that expands the response with storages, bridges, and templates, and by tying it to the two-call workflow. It does not add format details for credential_id, which the schema already covers.

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 provisioning options a Proxmox VE credential can reach') and enumerates exactly what is returned: host nodes with CPU/memory capacity, static instance-type presets, and node-scoped storages, bridges, and templates. This clearly separates it from siblings like list_morpheus_options, list_upcloud_options, and list_instance_types.

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?

Gives an explicit two-step workflow: call before create_proxmox_cluster, first without a node to pick one, then with the chosen node to pick storage, bridge, and template. The when-to-use and the sequencing relative to the sibling creation tool are both spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.