Skip to main content
Glama

List USB devices

proxmox_list_node_usb_devices
Read-only

List a node's USB devices for passthrough, including vendor:product IDs, bus/port paths, speed and serial, and filter by name or ID to select devices for VM attachment.

Instructions

List a node's USB devices for passthrough: vendor:product ID, manufacturer and product names, bus/port path, speed and serial. Pass a device to a VM by ID (host=vendor:product) or port (host=bus-port), or via a USB resource mapping.

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

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description's real contribution is enumerating the returned fields (vendor:product, manufacturer, product, bus/port path, speed, serial), which matters because no output schema exists. It stops short of stating permissions, behavior on nodes without USB devices, or whether the list is filtered — modest added value over the annotations.

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 dense sentences, front-loaded with the operation and immediately followed by the returned data and the passthrough formats. No filler, though the second sentence leans toward downstream configuration advice rather than describing this tool's own invocation.

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 simple read-only listing tool with no output schema, the description supplies the return-field inventory and the identifier formats an agent needs to act on results. The only gap is the undocumented 'fields' parameter, which neither schema nor description explains.

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 67%: node carries a default and a pointer to proxmox_list_nodes, and search is documented, while fields is undocumented in both schema and description. The description's mention of vendor:product and bus-port formats relates to passthrough configuration rather than to any input parameter, so it adds no meaning the schema lacks.

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 a node's USB devices) and adds the intent 'for passthrough', which separates it from generic node-inventory siblings like proxmox_list_node_pci_devices or proxmox_list_node_network without naming them. The purpose is unambiguous, though an explicit pointer to the PCI-device sibling would make the differentiation sharper.

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 phrase 'for passthrough' implies the use case, and the second sentence explains how to consume the results (host=vendor:product, host=bus-port, or a USB resource mapping). However, there is no explicit when-to-use/when-not guidance versus sibling listing tools and no stated prerequisites, so usage is only implied.

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