Skip to main content
Glama

Get a resource mapping

proxmox_get_resource_mapping
Read-only

Fetch a specific PCI, USB, or directory resource mapping, including per-node entries and digest, to inspect Proxmox VE resource assignments.

Instructions

Get one PCI, USB or directory resource mapping with its per-node entries and digest.

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>",
      "id": "<id>"
    },
    "name": "proxmox_get_resource_mapping"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMapping ID
kindYesMapping kind: pci (passthrough devices), usb, or dir (virtiofs directories)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description does add value by disclosing that the response includes per-node entries and a digest, but it says nothing about mutation semantics, whether a missing mapping errors or returns empty, or the effect of the non-idempotent hint on a read operation.

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?

A single front-loaded sentence with no filler: verb, scope, accepted kinds, and response shape in one pass. Nothing could be removed without losing information.

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 two-parameter read tool with full schema coverage and annotations covering the safety profile, the description is nearly complete; it even compensates for the absent output schema by naming the returned fields. Only the missing linkage to the list sibling keeps it short of full marks.

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% and both required parameters are documented in the schema, including the kind enum with per-value meaning (pci/passthrough, usb, dir/virtiofs). The description only restates the kinds, adding no format, casing, or lookup semantics beyond the schema, so the baseline of 3 applies.

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 (Get) and resource (resource mapping), scoped to a single item, and enumerates the three kinds (PCI, USB, directory) while noting the payload includes per-node entries and digest. The word "one" implicitly separates it from a list-style sibling, though that sibling is never named.

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?

Usage is only implied: the singular "Get one ... mapping" signals single-item retrieval as opposed to enumeration, but there is no explicit when-to-use statement, no prerequisites (e.g., mapping must exist), and no named alternative such as the list-resource-mappings sibling. Adequate but leaves routing to inference.

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