Unofficial-Proxmox-MCP

pve_recommend_placement

Analyze cluster resource congestion and recommend the optimal node for placing new workloads based on required cores, RAM, and disk space.

Instructions

Analyze cluster resource congestion and recommend the optimal node for placing new workloads.

Args: required_cores: Number of virtual CPU cores needed. required_mem_mb: RAM in megabytes required. required_disk_gb: Storage in gigabytes required.

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": "pve_recommend_placement"
  }
}

Input Schema

Name	Required	Description	Default
`required_cores`	No
`required_mem_mb`	No
`required_disk_gb`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 9, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it: it never states that this is a non-mutating analysis, whether storage already provisioned affects the answer, how congestion is measured (CPU vs memory vs disk), or how ties/no-fit cases are handled. Only the inputs are disclosed, nothing about the operation's behavior or side effects.

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?

One front-loaded purpose sentence followed by a minimal parameter list; nothing is padded or repeated. The Args block is justified because the schema has no parameter descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the three simple optional parameters are covered. But for a decision-support tool with zero annotations, the definition leaves the agent without guidance on when to invoke it instead of inspecting nodes directly, or on the limits of the recommendation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the schema provides only bare titles — but the description's Args block supplies the missing meaning, including units (virtual CPU cores, RAM in megabytes, storage in gigabytes) that the titles alone do not convey. It omits the defaults (2 / 2048 / 20) declared in the schema, which would have told an agent the tool works with zero arguments.

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 gives a specific verb pair (analyze/recommend) and a concrete resource (placement node for new workloads), and 'Analyze cluster resource congestion' distinguishes it from inventory siblings like pve_list_nodes or pve_get_node_status. An agent can tell what it produces: a node recommendation for a sizing request.

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 — 'placing new workloads' hints that it is called before pve_create_vm/pve_create_lxc, but no explicit trigger, prerequisite, or exclusion is stated. It never says what to do when the cluster is full, when no node is suitable, or how it relates to the listing/status siblings.

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