Skip to main content
Glama

pve_mapping_usb_create

Create a USB device passthrough mapping for a Proxmox cluster; dry-run returns a plan, confirm executes.

Instructions

MUTATION: create a USB cluster passthrough mapping. Dry-run by default (returns a PLAN); confirm=True executes and returns {"status": "ok", "result": null} (no further payload). Additive — MEDIUM risk, since a mismatched USB device ID can prevent VMs from acquiring the device. To modify an existing mapping use pve_mapping_usb_update; to remove one use pve_mapping_usb_delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mapNoUSB device map string(s) defining the physical device(s) covered by this mapping
confirmNoFalse (default) returns a dry-run PLAN only; True executes the creation
mapping_idYesUnique ID for the new USB cluster passthrough mapping
descriptionNoOptional free-text description stored with the mapping
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, description fully discloses mutation, dry-run behavior, return values (PLAN vs success response), and risk of mismatched USB device ID. Comprehensive behavioral info.

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?

Extremely concise yet information-rich: front-loads mutation, then behavior, risk, and sibling guidance. Every sentence serves a purpose with no redundancy.

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?

Covers key behavioral aspects well given no annotations and presence of output schema. Minor gap: does not mention whether mapping_id uniqueness is enforced or retry behavior, but otherwise complete.

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 100%, so parameters are already well-documented. Description adds no additional meaning beyond what schema provides, meeting baseline expectation.

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?

The description clearly states the tool creates a USB cluster passthrough mapping, using 'MUTATION:' to indicate write operation. It distinguishes from siblings (update, delete) by naming them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: dry-run by default, confirm=True to execute, risk level (MEDIUM), and when to use update/delete instead. Clear usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server