Skip to main content
Glama

Check container feature support

proxmox_check_container_feature
Read-only

Check whether a container's storage supports snapshots, linked cloning, or full copying from an optional snapshot, and list eligible nodes before snapshot or clone operations.

Instructions

Check whether a container's storage supports snapshots, cloning (linked) or copying (full clone), optionally from a given snapshot, and on which nodes. Useful before proxmox_create_snapshot or proxmox_clone_container.

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": {
      "vmid": "<vmid>",
      "feature": "<feature>"
    },
    "name": "proxmox_check_container_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode the guest is on. Looked up automatically from the VMID when omitted.
vmidYesVM or container ID (VMID), e.g. 100
featureYesFeature to check
snapnameNoCheck from this snapshot

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 and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing that results are reported per node ('and on which nodes') and can be scoped to a snapshot, though it does not explain why idempotentHint is false for an ostensibly read-only check or what the response looks like.

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 sentences, no filler: the capability statement comes first, the downstream use case second. Every clause carries information an agent needs.

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 four-parameter read-only check with a fully documented schema and no output schema, the definition covers purpose, scope, and intended call sites adequately. The only residual gap is the shape of the per-node result, which an agent must discover by calling it.

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%, so every parameter including the feature enum and the optional snapname is already documented. The description reinforces the snapshot scoping ('optionally from a given snapshot') but adds no syntax or constraint detail beyond the schema, so the baseline of 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 ('Check whether') and a precise resource ('a container's storage'), then enumerates the three features checked (snapshot, linked clone, full copy) and the node-level result. The word 'container' distinguishes it from the sibling proxmox_check_vm_feature without needing the schema.

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?

Gives concrete downstream context: 'Useful before proxmox_create_snapshot or proxmox_clone_container', which tells the agent exactly when to reach for it. It stops short of saying when not to use it or what to do if the check fails, so it is clear context rather than a full decision rule.

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