Skip to main content
Glama

List PCI devices

proxmox_list_node_pci_devices
Read-only

List a Proxmox node's PCI devices to plan passthrough: view addresses, vendor/device IDs, classes, IOMMU groups and vGPU support, filtered by class or mdev capability.

Instructions

List a node's PCI devices for passthrough planning: address, class, vendor/device names and IDs, IOMMU group (with the other devices in the same group, which must be passed through together) and whether it supports mediated devices (vGPU). Memory controllers, bridges and processors are hidden unless all=true. IOMMU group -1 means IOMMU is off.

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

Input Schema

NameRequiredDescriptionDefault
allNoInclude memory controllers, bridges and processors (hidden by default)
rawNoReturn the full unprocessed objects from the API (larger)
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
classNoOnly this class: a name (display, network, storage, multimedia, serial-bus, accelerator...) or hex class code prefix, e.g. 03 or 0300
limitNoMaximum number of results (default 500)
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
mdev_onlyNoOnly devices that support mediated devices (vGPU)

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 establish that this is a read-only, non-open-world operation. The description adds substantial behavioral context beyond that: default hiding of memory controllers, bridges and processors, the requirement that devices in the same IOMMU group be passed through together, and the meaning of IOMMU group -1.

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?

The description is compact and front-loaded, moving from the core purpose to returned fields and then edge cases. Every sentence carries useful information, with no filler or repetition.

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 an eight-parameter list tool with no output schema, the description covers the important return fields and domain-specific caveats well. It could say a bit more about result volume or how raw output differs, but the schema already documents the parameters and defaults.

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 88%, so parameter meanings are already largely documented. The description reinforces all=true and mentions mediated-device support, but does not add much beyond the schema for class, raw, limit, search, fields, or mdev_only; the IOMMU group -1 note is primarily about returned data rather than parameters.

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 a node's PCI devices') and enumerates the returned fields, so the agent knows exactly what this tool produces. It is clearly distinguishable from siblings like USB device listing and mdev type listing by the PCI-device scope and passthrough-planning framing.

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?

The phrase 'for passthrough planning' supplies a clear use context, and the hidden-device behavior explains when to set all=true. It does not explicitly compare against alternatives such as proxmox_list_node_usb_devices or proxmox_list_node_mdev_types, so it stops short of full routing guidance.

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