Skip to main content
Glama

pve_mapping_pci_create

Create a new PCI cluster passthrough mapping for hardware device passthrough. Dry-run by default; set confirm=true to apply the mapping.

Instructions

MUTATION: create a PCI 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 IOMMU/VFIO map can prevent VMs from starting. To modify an existing mapping use pve_mapping_pci_update; to remove one use pve_mapping_pci_delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mapNoPCI 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 PCI 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?

No annotations provided, but description fully covers behavior: mutation, dry-run default, confirm execution, response format, and risk of mismatched IOMMU/VFIO affecting VM startup.

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?

Very concise: two sentences plus a sibling reference. Front-loaded with 'MUTATION'. No wasted words.

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 creation behavior, risk, siblings, and response. Output schema exists, so return values are covered. Could mention uniqueness constraint on mapping_id, but otherwise complete for a create action.

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 in schema. Description adds value by explaining confirm parameter behavior and risk, but does not add depth to other parameters beyond what schema provides. Baseline 3.

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?

Description clearly states it creates a PCI cluster passthrough mapping. The verb 'create' is explicit, and it distinguishes from siblings by mentioning update and delete analogous tools.

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: use for creation, use update for modifications, use delete for removal. Also explains the dry-run default and confirm flag behavior.

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