Skip to main content
Glama

Get a custom CPU model

proxmox_get_custom_cpu_model
Read-only

Fetch one custom CPU model definition, including its digest, by name with or without the 'custom-' prefix to inspect Proxmox VE custom CPU settings.

Instructions

Get one custom CPU model definition, including its 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": {
      "name": "<name>"
    },
    "name": "proxmox_get_custom_cpu_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesModel name, with or without the 'custom-' prefix

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 and openWorldHint=false, so the safe-read profile is covered. The description adds that the returned definition includes its digest, which is useful beyond the annotations, but says nothing about behavior when the model name doesn't exist or what the payload shape is.

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 short sentence, front-loaded with the verb and resource, with the digest detail appended rather than buried. No filler.

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 single-parameter read tool with no output schema, this is nearly sufficient: the annotations carry the safety profile and the description notes the digest in the return. Only the not-found behavior is left unaddressed, which is a minor gap for a lookup tool.

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 the schema itself documents the 'with or without the custom-' prefix handling, so the description legitimately adds nothing about the single `name` parameter. Baseline 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 and resource ('Get one custom CPU model definition') and adds that the digest is included in the result, which distinguishes it from the sibling list tool by scope ('one' vs. enumeration). It doesn't explicitly name the list sibling, so it stops short of full sibling differentiation.

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?

The singular framing implies this is the per-item lookup tool and the list sibling covers enumeration, but the description never says when to use it or what to do instead (e.g. list first to discover names). Usage is inferable, not stated.

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