Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

list_install_media

Read-onlyIdempotent

List ISO images, container templates, storages, network bridges and the next free VMID so you can choose what new guests are created from.

Instructions

What new guests can be made from: ISO images, container templates, storages, network bridges and the next free VMID.

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": {
      "host": "<host>"
    },
    "name": "list_install_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.
nodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description does add one piece of behavioral information beyond them — that the response includes the next free VMID alongside media/storage/bridge inventories — which is useful for planning a create call. It says nothing about scope (per-host vs per-node) or response shape otherwise.

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

Conciseness3/5

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

It is a single compact sentence with no wasted words, but it opens with an awkward dependent fragment ('What new guests can be made from:') rather than a front-loaded action verb, which costs a little immediate clarity.

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, so the description's enumeration of returned content types carries real weight and is reasonably complete. However, for a two-parameter tool it leaves the 'node' parameter and the host-vs-node scoping unexplained, so an agent can call it but may pass node incorrectly or unnecessarily.

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 coverage is only 50%: 'host' is documented ('The host's id, from list_hosts.') but 'node' has no description at all. The description mentions neither parameter, so it does not compensate for the gap — it is unclear whether 'node' scopes the results to a single cluster node or is optional filtering.

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 the concrete resource set being listed (ISO images, container templates, storages, network bridges, next free VMID), which lets an agent infer this enumerates installation sources for new guests. The verb 'list' is only implicit in the fragment phrasing and there is no differentiation from siblings such as get_cloud_image or download_iso, so it stops short of a 5.

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 statement of when to call this versus alternatives — nothing says to use it before create_vm/create_container, or how it differs from get_cloud_image or list_guests. The agent must infer the usage context entirely from the noun phrase.

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