Skip to main content
Glama
Sign In
Proxmox VE MCP server

Proxmox VE MCP server

by askmojood
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

What needs attention

needs_attention
Read-onlyIdempotent

Finds Proxmox VE guests with no backup coverage, overdue backups, stopped production status, old snapshots, storage pressure, or low memory so you can address risks.

Instructions

Guests no backup job covers, overdue backups, production guests that are stopped, old snapshots, storage filling up, and guests short of memory.

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

Input Schema

NameRequiredDescriptionDefault
backup_daysNoa backup older than this many days counts as overdue

Output Schema

NameRequiredDescriptionDefault
memory_highYes
old_snapshotsYes
backups_overdueYesin a backup job, but no backup newer than the limit
storage_fillingYes
production_stoppedYestagged "prod" and not running
not_in_any_backup_jobYesguests no backup job covers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description's main added value is defining what 'attention' means via the six issue classes, which is genuinely useful. It still leaves the judgment thresholds undefined — what counts as 'storage filling up' or 'short of memory' is never stated, and only the backup window is governed by a documented parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

One dense sentence that front-loads the issue categories with no filler or repetition. It reads as a noun fragment rather than a full statement of what is returned, which slightly reduces clarity for an agent unfamiliar with the tool family.

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?

With an output schema present and annotations covering the safety profile, the description needn't explain return values or side effects. However, for a composite diagnostic tool it leaves out how findings are prioritized or grouped and what the implicit thresholds are, which an agent may need in order to interpret or relay results correctly.

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?

The single parameter has 100% schema coverage with a clear description, default of 7, and a 1-90 bound, so the schema already carries full semantics. The description's phrase 'overdue backups' points at the concept but adds no syntax or tuning guidance beyond what the schema states.

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?

The description enumerates the concrete conditions the tool surfaces (uncovered guests, overdue backups, stopped production guests, old snapshots, storage pressure, memory shortage), which is a much more specific statement of purpose than the bare name. It does not, however, distinguish this from the sibling 'overview' tool, so an agent comparing the two gets no routing signal from the description.

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: an agent can infer 'use this to find problems' from the list of problems, but there is no explicit when-to-use statement, no mention of when to prefer 'overview' or 'find_guests' instead, and no stated prerequisites or cost of calling it.

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