Skip to main content
Glama

List resource mappings

proxmox_list_resource_mappings
Read-only

Lists Proxmox cluster PCI, USB, and virtiofs directory resource mappings that link logical names to node devices for VM migration; optionally validates mappings against a node.

Instructions

List cluster resource mappings of one kind: PCI or USB devices, or directories (for virtiofs), each mapping a logical name to the device/path on every node. VMs reference them as e.g. hostpci0: mapping=, which allows migration. With check_node, Proxmox validates the entries for that node.

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": {
      "kind": "<kind>"
    },
    "name": "proxmox_list_resource_mappings"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesMapping kind: pci (passthrough devices), usb, or dir (virtiofs directories)
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
check_nodeNoValidate the mappings against this node's hardware and report problems

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/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 real behavior beyond that by explaining that check_node triggers validation of entries against a specific node's hardware and reports problems — a side effect an agent would not learn from the annotations. It still omits result shape and whether validation output is mixed into the listing.

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?

Two tightly packed sentences that front-load the core action and scope ("of one kind"), then add migration rationale and the check_node caveat. Every clause carries information; only the illustrative hostpci0 syntax is arguably expendable.

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?

With no output schema, the description carries the burden of describing what comes back, and it never indicates the return structure — whether entries are grouped per node, per kind, or flattened — which matters for a tool whose whole concept is per-node mapping. Annotations plus the kind/check_node explanation make it callable, but not fully predictable.

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 coverage is 75%, so baseline is 3. The description reinforces kind semantics and the check_node validation behavior, but it is largely redundant with the enum and property descriptions already in the schema, and it says nothing about the undocumented "fields" parameter or how "search" interacts with node-scoped results.

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?

States a specific verb and resource ("List cluster resource mappings") and enumerates the three mapping kinds (PCI, USB, dir/virtiofs), plus explains what a mapping is: a logical name bound to a device/path on every node. It does not explicitly contrast with the singular sibling proxmox_get_resource_mapping, so the list-vs-get distinction rests on naming alone.

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?

The description supplies useful motivation (VMs reference mappings as hostpci0: mapping=<id>, which enables migration) and explains what happens when check_node is supplied. It never states when to prefer this tool over proxmox_get_resource_mapping or proxmox_list_directory_mounts, and gives no exclusions or prerequisites, so usage is implied rather than directed.

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