Skip to main content
Glama

List custom CPU models

proxmox_list_custom_cpu_models
Read-only

List cluster-wide custom CPU models, including base model and flag changes, to identify which custom- CPU types VMs can use.

Instructions

List cluster-wide custom CPU models (base model plus flag changes). VMs use them as cpu: custom-. Related: proxmox_get_node_capabilities for built-in models and flags.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
fieldsNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.7/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 and the description only needs to add context. It does add useful facts — cluster-wide scope and the cpu: custom-<name> naming convention — but says nothing about return shape, ordering, or what an empty list means. Adequate but not rich beyond 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the primary assertion front-loaded and the alternative relegated to a trailing "Related:" clause. Every clause carries information; nothing is padding.

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?

A read-only list tool with no output schema and no nested objects is relatively simple, so the description is close to sufficient. However, two of three parameters are undocumented and the return shape of the custom-model objects is unstated, which leaves gaps an agent would hit immediately on invocation.

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 description coverage is only 33%: only `raw` is documented ("Return the full unprocessed objects from the API (larger)"), while `fields` and `search` are undocumented anywhere. The description does not compensate for those two parameters at all, so it neither adds nor damages meaning. Below the high-coverage baseline, so a low 3 is generous but defensible given zero required parameters.

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 cluster-wide custom CPU models") and adds scope detail — base model plus flag changes, cluster-wide. It also explains how the results are consumed ("VMs use them as cpu: custom-<name>"), which separates it from a generic model listing, though it never explicitly contrasts with the singular proxmox_get_custom_cpu_model sibling.

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

Usage Guidelines4/5

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

Provides a concrete alternative for a different need: "proxmox_get_node_capabilities for built-in models and flags." That tells the agent when this tool is not the right one. It stops short of an explicit when-to-use rule (e.g., call this to discover names before fetching one model), so it is clear context rather than full routing guidance.

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