Skip to main content
Glama

Get next free VMID

proxmox_get_next_vmid
Read-only

Get the next free VM or container ID, or check whether a specific ID is available before assigning it.

Instructions

Get the next free VM/container ID, or check whether a specific ID is free.

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

Input Schema

NameRequiredDescriptionDefault
vmidNoCheck whether this ID is free instead

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4/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 safety is covered. The description adds the dual-mode behavior but does not say whether a successful lookup reserves or consumes the ID, nor what happens if the requested vmid is already taken — meaningful gaps for an allocation-adjacent tool.

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 sentence, zero filler, with the primary purpose front-loaded and the alternate mode appended. 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 one-parameter read-only tool with no output schema, the description covers both invocation modes cleanly. It could be stronger by stating what is returned in each case (an ID versus a free/busy result), but that is the only real omission.

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 single parameter is already documented as 'Check whether this ID is free instead'. The description restates that meaning without adding format, range (100+), or behavior when the ID is occupied, so baseline 3 applies.

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?

States a specific verb (get) and resource (next free VM/container ID) and covers the secondary mode (check a specific ID is free). An agent can tell exactly what the tool returns conceptually without opening the schema, and no sibling tool in the list does ID allocation.

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?

The two modes are clearly framed: call with no argument to allocate the next free ID, call with vmid to test a specific one. It doesn't name alternatives or exclusions, but there is no obvious competing sibling, so the guidance is sufficient without them.

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